Systems and methods for latency reduction

ABSTRACT

Systems and methods presented herein provide for reducing latency in wireless service through a communication link comprising a Modem Termination System (MTS) and a modem. The communication link is coupled with a virtualized wireless link. In one embodiment, a method includes transferring a buffer status report (BSR) from a user equipment (UE) through the communication link to a control portion of the virtualized wireless link, generating a wireless grant to allow the data of the UE through virtualized wireless link, and generating a backhaul grant for the UE to transfer data through the communication link based on the wireless grant information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/126,889, filed Sep. 10, 2018, which application is a continuation ofPCT application no. PCT/US 17/21918, filed Mar. 10, 2017, whichapplication claims the benefit of U.S. provisional application No.62/357,770 filed Jul. 1, 2016, U.S. provisional application No.62/345,634 filed Jun. 3, 2016, U.S. provisional application No.62/353,755 filed Jun. 23, 2016, U.S. provisional application No.62/339,463 filed May 20, 2016, and U.S. provisional application No.62/306,360 filed Mar. 10, 2016, the disclosures and benefits of whichare incorporated in their entireties by reference herein. PCTapplication no. PCT/US 17/21918 also claims the benefit of U.S.application Ser. No. 15/236,147 filed Aug. 12, 2016, U.S. applicationSer. No. 15/447,419 filed Mar. 2, 2017, U.S. application Ser. No.15/453,146 filed Mar. 8, 2017, and U.S. application Ser. No. 15/454,668filed Mar. 9, 2017, the disclosures and benefits of which are alsoincorporated in their entireties by reference herein.

TECHNICAL FIELD

The present invention relates to systems and methods for latencyreduction.

BACKGROUND

Mobile Network Operators (MNOs) operate a mobile core to providewireless service to a variety of wireless user equipment (UEs, such ascell phones, laptop computers, tablet computers, etc.). The wirelessnetworks of these MNOs exist in a variety of forms and operate using avariety of modulations, signaling techniques, and protocols, such asthose found in Wifi, 3G, 4G, 5G and Long Term Evolution (LTE) networks.Some MNOs even operate with Multiple-System Operators (MSOs),Telecommunications Companies (telcos), satellite operators (includinghigh speed satellite broadband services), fiber operators, and UAVinternet providers, collectively referred to as “Operators”. Forexample, Operators routinely provide internet services to the MNOs forbackhaul traffic, while the MNO provides wireless services for theOperator. In addition, some Operators operate both the wired servicesand MNO services.

Now, MSOs are even providing “small cells” such that a UE cancommunicate through its MNO via an MSO. For example, an MSO may deployan antenna/interface that a UE can communicate with via its respectivewireless protocol. The MSO packages the communications between the UEand the MNO via the MSO's protocol, for example Data Over Cable ServiceInterface Specification (DOCSIS). However, latency is incurred becauseof the serial nature of data transfer grants between DOCSIS and thewireless protocol.

Now, MSOs are even providing “small cells” such that a UE cancommunicate through its MNO via an MSO. For example, an MSO may deployan antenna/interface that a UE can communicate with via its respectivewireless protocol. The MSO packages the communications between the UEand the MNO via the MSO's protocol, for example Data Over Cable ServiceInterface Specification (DOCSIS).

In some instances, functionality of a small cell may be spread across acommunication link via virtualization of the components thereof. But,granting data transfer requests from UEs through the communication linkis problematic because latency incurs from the serial nature of datatransfer grants between the wireless protocol and that of thecommunication link.

Now, Operators are even providing “small cells” such that a UE cancommunicate through its MNO via the Operator. For example, an MSO maydeploy an antenna/interface that a UE can communicate with via itsrespective wireless protocol. The MSO packages the communicationsbetween the UE and the MNO's mobile core via the MSO's protocol, forexample Data Over Cable Service Interface Specification (DOCSIS).However, inefficiencies in the communication session setups of theOperator and the MNO create latencies that negatively affect the user'sQuality of Experience (QoE).

Mobile Network Operators (MNOs) provide wireless service to a variety ofuser equipment (UEs), and operate using a variety of techniques such asthose found in 3G, 4G LTE networks. The wireless service network canconsist of macro and/or small cells.

Some MNOs operate with Multi System Operators (MSOs) of the cableindustry for backhauling traffic for wireless networks. The MSO packagesthe communications between the UE and the MNO via the MSOs protocol, forexample Data Over Cable Service Interface Specification (DOCSIS).

Since the wireless and backhaul networks are controlled by separateentities, DOCSIS backhaul networks and wireless radio networks each lackvisibility into the other's network operations and data. This causes thescheduling algorithms for the wireless and DOCSIS network to operateseparately, which can result in serial operations during the transfer ofdata from UE to the mobile core. The DOCSIS network does not haveinsights into the amount and the priority of wireless data beingbackhauled, since this knowledge is only known to the wireless portionof the network.

SUMMARY

Systems and methods presented herein provide for a latency reduction inwireless service through a request-grant based communication link, forexample a DOCSIS communication link. In one embodiment, a methodincludes linking a modem to a Modem Termination System (MTS) via theDOCSIS communication link and detecting, at the modem, a message from awireless service link indicating that a user equipment (UE) has data totransmit to a Mobile Network Operator (MNO). Other embodimentscontemplated utilizing an optical network. An optical network may beformed with, for example, an Optical Network Terminal (ONT) or anOptical Line Termination (OLT), and an Optical Network Unit (ONU), andmay utilize optical protocols such as EPON, RFOG, or GPON. Embodimentsalso contemplated exist in other communication systems capable ofbackhauling traffic, for example, a satellite operator's communicationsystem. To simplify description, a termination unit such as a CMTS, anONT, an OLT, a Network Termination Units, a Satellite Termination Units,and other termination systems are collectively called a “ModemTermination System (MTS)”. To simplify description a modem unit such asa satellite modem, a modem, an Optical Network Units (ONU), a DSL unit,etc. collectively called a “modem.” Further, to simplify description aprotocol such as DOCSIS, EPON, RFOG, GPON, Satellite Internet Protocol,is called a “protocol.”

In an embodiment, the present system and method handles a data requestfor transmitting from a modem to a mobile core via the wireless servicelink. In an embodiment, the processing of the data request from themodem occurs at least in part at the MTS. The system and method arecapable of processing a wireless request to result in a wireless grantsubstantially simultaneous to the backhaul negotiation of thetransmission of UE data over the backhaul network.

In an embodiment, the UE is an LTE wireless device in wirelesscommunication with an eNodeB, although it will be understood that thepresent invention is equally applicable for use with 2G, 3G, 5G, andother wireless protocol systems.

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

Systems and methods presented herein provide for reducing latency inwireless service through a request-grant based communication link, forexample a DOCSIS communication link. In one embodiment, thecommunication link comprises a virtualized Modem Termination System(vMTS) and a modem. The communication link is coupled with a virtualizedwireless link (e.g., configured from a remote small cell and a centralsmall cell). Other embodiments contemplated utilizing an opticalnetwork. An optical network may be formed with, for example, an OpticalNetwork Terminal (ONT) or an Optical Line Termination (OLT), and anOptical Network Unit (ONU), and may utilize optical protocols such asEPON, RFOG, or GPON. Embodiments also contemplated exist in othercommunication systems capable of backhauling traffic, for example, asatellite operator's communication system. To simplify description, atermination unit such as a CMTS, an ONT, an OLT, a Network TerminationUnits, a Satellite Termination Units, and other termination systems arecollectively called a “Modem Termination System (MTS)”. To simplifydescription a modem unit such as a satellite modem, a modem, an OpticalNetwork Units (ONU), a DSL unit, etc. collectively called a “modem.”Further, to simplify description a protocol such as DOCSIS, EPON, RFOG,GPON, Satellite Internet Protocol, is called a “protocol.”

In some embodiments, the present system and method handles transferringa bandwidth request message, such as a buffer status report (BSR), froma UE through the communication link to a control portion of thevirtualized wireless link, for example residing with the central SmallCell (cSC). For example, in one embodiment, the control portion of thevirtualized wireless link signals the vMTS to generate a grant, (e.g., abackhaul grant), for the transmission of the UE data on thecommunication link. The control portion of the virtualized wireless linkalso generates a wireless grant for the UE to transfer the data on thevirtualized wireless link. It will be understood that the controlportion of the virtualized wireless link, e.g., the central Small Cell(cSC), may be configured in a cloud computing system in communicationwith the wireless core or may be configured in the wireless core. Inbackhaul wireless core integrated embodiment, the control portion of thevirtualized wireless link may be configured with an MTS or vMTS.

In another embodiment, the control portion of the virtualized wirelesslink signals of a grant for the transmission of the UE data on thecommunication link. Again, the control portion of the virtualizedwireless link also generates a wireless grant for the UE to transfer thedata on the virtualized wireless link.

In a separate embodiment, a mediator intercepts or generates a copy ofone or both of the BSR sent from the UE to the cSC and the UL grant sentfrom the cSC to the UE. The mediator unpacks or otherwise decodes all ora portion of the BSR and/or the UL grant to provide data to the vMTS forthe generation of a MAP or an unsolicited grant for transmission to themodem. It will be understood that the mediator may be configured withthe vMTS or the cSC, configured between the vMTS and the cSC, orconfigured between the RPD and the vMTS.

In another embodiment, the functionality detailed above for the mediatoris integrated into the vMTS itself, such that the vMTS unpacks orotherwise decodes all or a portion of the BSR and/or the UL grant so thevMTS may generate a MAP or an unsolicited grant for transmission to themodem. In this way the modem is prepared for the transmission of UL dataas soon as it arrives at the modem thereby significantly reducinglatency.

In a separate embodiment, the RPD is replaced with a Remote Device (RD)configured to implement both the PHY and MAC layers (similar to PHY 127and MAC 126 of FIG. 12) and the mediator is configured between the RDand the vMTS. In this embodiment the mediator intercepts or generates acopy of one or both of the BSR sent from the UE to the cSC and the ULgrant sent from the cSC to the UE. The mediator unpacks or otherwisedecodes all or a portion of the BSR and/or the UL grant to provide datato a remote device (RD) for the generation of a MAP or an unsolicitedgrant for transmission to the modem.

In another embodiment, the functionality for the mediator, detailedimmediately above, is integrated into the Remote Device itself, suchthat the RD unpacks or otherwise decodes all or a portion of the BSRand/or the UL grant so the RD may generate a MAP or an unsolicited grantfor transmission to the modem. In this way the modem is prepared totransmit UL data as soon as it arrives at the modem, therebysignificantly reducing latency.

In an embodiment, the UE implements LTE protocol, although it will beunderstood that the present invention is equally applicable for use with2G, 3G, 5G, Wi-Fi and other wireless protocol systems. In an embodiment,the Modem 102 implements DOCSIS protocol, although it will be understoodthat the present invention is equally applicable for use with satellite,EPON, GPON, and other wired protocol systems.

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

Systems and methods presented herein provide for expediting the setup ofa wireless service through a request-grant based communication link, forexample, a DOCSIS communication link. In one embodiment, a methodcomprises intercepting setup information for a wireless session from amobile core (e.g., operated by an MNO) servicing the UE, initiating acommunication session between a Modem Termination System (MTS) and amodem based on the intercepted setup information to support aforthcoming wireless session, and providing the wireless session throughthe communication session setup.

Other embodiments contemplated utilizing an optical network. An opticalnetwork may be formed with, for example, an Optical Network Terminal(ONT) or an Optical Line Termination (OLT), and an Optical Network Unit(ONU), and may utilize optical protocols such as EPON, RFOG, or GPON.Embodiments also contemplated exist in other communication systemscapable of backhauling traffic, for example, a satellite operator'scommunication system. To simplify description, a termination unit suchas a CMTS, an ONT, an OLT, a Network Termination Units, a SatelliteTermination Units, and other termination systems are collectively calleda “Modem Termination System (MTS)”. To simplify description a modem unitsuch as a satellite modem, a modem, an Optical Network Units (ONU), aDSL unit, etc. collectively called a “modem.” Further, to simplifydescription a protocol such as DOCSIS, EPON, RFOG, GPON, SatelliteInternet Protocol, is called a “protocol.”

In an embodiment, the UE is an LTE wireless device, although it will beunderstood that the present invention is equally applicable for use with2G, 3G, 5G, Wi-Fi and other wireless protocol systems.

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

Other embodiments contemplated utilizing an optical network. An opticalnetwork may be formed with, for example, an Optical Network Terminal(ONT) or an Optical Line Termination (OLT), and an Optical Network Unit(ONU), and may utilize optical protocols such as EPON, RFOG, or GPON.Embodiments also contemplated exist in other communication systemscapable of x-hauling traffic, examples include without limitationsatellite operator's communication systems, Wi-Fi networks, opticalnetworks, DOCSIS networks, MIMO communication systems, microwavecommunication systems, short and long haul coherent optic systems, etc.X-hauling is defined here as any one of or a combination offront-hauling, backhauling, and mid-hauling. To simplify description, atermination unit such as a CMTS, an ONT, an OLT, a Network TerminationUnits, a Satellite Termination Units, and other termination systems arecollectively called a “Modem Termination System (MTS)”. To simplifydescription a modem unit such as a satellite modem, a modem, an OpticalNetwork Units (ONU), a DSL unit, etc. collectively called a “modem.”Further, to simplify description a protocol such as DOCSIS, EPON, RFOG,GPON, Satellite Internet Protocol, is called a “protocol.”

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary wireless service link throughan MTS.

FIG. 2 is a flowchart illustrating an exemplary process operable with amodem of the wireless service link of FIG. 1.

FIG. 3 is a flowchart illustrating an exemplary process operable withthe MTS of FIG. 1.

FIG. 4 is an exemplary communication diagram of the wireless servicelink through an MTS of FIG. 1.

FIG. 5 is a block diagram of an exemplary buffer status report (BSR)operable with the wireless service link of FIG. 1.

FIG. 6 is another exemplary communication diagram of the wirelessservice link through the MTS of FIG. 1.

FIG. 7 is a block diagram of an exemplary computing system in which acomputer readable medium provides instructions for performing methodsherein.

FIG. 8 is a block diagram of a cable network.

FIG. 9 is an exemplary communication diagram of the wireless servicelink employing WiFi.

FIG. 10 is a block diagram of exemplary components implementing avirtualized wireless link with a communication link.

FIG. 11A is a block diagram of an exemplary protocol stack of a virtualbase station (vBS).

FIG. 11B is a block diagram of another exemplary protocol stack of avirtual base station (vBS).

FIG. 12A is a block diagram of an exemplary protocol stack of a RemotePHY Device (RPD) and vMTS.

FIG. 12B is a block diagram of an exemplary protocol stack of a RemoteMAC PHY Device (RMPD) and vMTS.

FIG. 13 is a flowchart illustrating an exemplary process operable withthe communication link of FIG. 10.

FIG. 14 is an exemplary communication diagram operable with componentsof FIG. 10.

FIG. 15 is a block diagram of an exemplary BSR.

FIG. 16 is a block diagram of an exemplary computing system in which acomputer readable medium provides instructions for performing methodsherein.

FIG. 17 is a block diagram of a communication system operable toimplement the embodiments herein.

FIG. 18 is a block diagram of an exemplary wireless service link throughan MTS.

FIG. 19 is a flowchart illustrating an exemplary process operable withthe MTS of FIG. 18.

FIG. 20 is an exemplary communication diagram of the wireless servicelink of FIG. 18.

FIG. 21 is a block diagram of an exemplary computing system in which acomputer readable medium provides instructions for performing methodsherein.

FIG. 22 is a block diagram of a communication system operable toimplement the embodiments herein.

FIG. 23 is an exemplary communication diagram of the wireless servicelink employing Wi-Fi.

FIG. 24 is an exemplary communication diagram of the wireless servicelink of FIG. 18 illustrating a network initiated session.

FIG. 25 shows one exemplary system configured to implement the presentprioritized grant assignment process, in an embodiment.

FIG. 26A is a more detailed view of the grant assignment system of FIG.25 processing multiple buffer status reports (BSRs) to generate a bulkrequest (REQ) for resources from a connected backhaul system, in anembodiment.

FIG. 26B is a more detailed view of the grant assignment system of FIGS.25 and 26B processing multiple logical channel groups (LCGs) from aplurality of user equipment (UEs) based on prioritization, in anembodiment.

FIG. 27 shows one exemplary priority processing system configured withina small cell, which processes upstream data for transmission after thereceipt of a partial grant, in and embodiment.

FIG. 28A is a communication diagram for the present grant assignmentprocess wherein the entire request (REQ) is granted, in an embodiment.

FIG. 28B is a communication diagram for the present grant assignmentprocess wherein a portion of the request (REQ) is granted, in anembodiment.

FIGS. 29A-C is a method flow detailing one exemplary process forgenerating a bulk request for resources, in an embodiment.

DETAILED DESCRIPTION

The figures and the following description illustrate specific exemplaryembodiments of the invention. It will thus be appreciated that thoseskilled in the art will be able to devise various arrangements that,although not explicitly described or shown herein, embody the principlesof the invention and are included within the scope of the invention.Furthermore, any examples described herein are intended to aid inunderstanding the principles of the invention and are to be construed asbeing without limitation to such specifically recited examples andconditions. As a result, the invention is not limited to the specificembodiments or examples described below. For example, the followingdescription is discussed as applied to an LTE-DOCSIS cooperative networkfor implementing latency reduction in wireless service between a userdevice and a wireless core. It will be appreciated that the presentlatency reduction in wireless service system and method may equally beapplied in systems utilizing macrocells, WiFi, satellite communicationsystems, optical backhaul systems (EPON, GPON, RFOG), MU-MIMO, lasercommunication, and even aerial vehicles such as unmanned aerial vehicles(UAV) and balloons that provide wireless and/or laser communication.That is, the present invention may be used in many wireless-to-backhaulsystems where at least one of the wireless system or backhaul systemutilizes a request-grant protocol for data transmission. For example,the following description is discussed as suggestive of an LTE-DOCSIScooperative network for expediting a grant assignment for a wirelessservice through a request-grant based communication link between a userdevice (e.g., a UE) and a wireless core (also called herein a “firstnetwork core”, e.g., a mobile core or Wi-Fi core). Generically, aLTE-DOCSIS cooperative network may be any first network-second networkcooperative communication system and is not limited to either LTE orDOCSIS networks. For example, the present system and method may be usedin a polling service based system, such as Real-Time Publish-Subscribe(RTPS). Polling is similar enough to a request-grant system that it maytake advantage of the present invention. One difference between arequest-grant system and a polling service system is polling occurswithout having to contend with other devices when a request is sent. Itwill be appreciated that the present system and method for prioritizedgrant assignment in wireless services may equally be applied in systemsutilizing microcells, picocells, macrocells, Wi-Fi, satellitecommunication systems, optical backhaul systems (EPON, GPON, RFOG),MU-MIMO, laser communication, and even aerial vehicles such as unmannedaerial vehicles (UAV) and balloons that provide wireless and/or lasercommunication. That is, the present invention may be used in manywireless-to-backhaul systems where at least one of the wireless systemor backhaul system utilizes a request-grant protocol for datatransmission.

FIG. 1 is a block diagram of an exemplary wireless service link 100including a mediator 109 configured with an MTS 106. It will beunderstood that mediator 109 may be integrated with or communicativelycoupled with MTS 106. The MTS 106 may be, for example, a CMTS, a FiberNode, a Fiber Hub, an optical network unit (ONU), or other terminationdevice. Mediator 109 may be implemented, for example, as a softwareagent in any of such devices. If mediator 109 is integrated with an MTS,integration may be via software or hardware.

A UE 105 may wirelessly communicate with other UEs (not shown) in awireless service network for the purpose of transmitting and/orreceiving data. A mobile core 107 (i.e., operated by an MNO) controlsthe operations of the UE 105 within the wireless network. This includes,among other things, managing subscription information (e.g., datacommunication, data plans, roaming, international calling, etc.) andensuring that the UE 105 can place calls and transmit data within thewireless network. Mediator 109 cooperates with the MTS to provide acommunication link between the UE 105 and the mobile core 107 such thatthe mobile core 107 can control the operations of the UE 105, forexample, when the UE 105 is within range of a “small cell” 103.

In the past, MNOs often maintained, operated, and controlled wirelessbase stations themselves for the purposes of providing communicationswith UEs. For example, an MNO employing LTE communications may operate aplurality of eNodeBs in an area to provide wireless services tosubscribing UEs in that area.

Now operators are capable of acting as backhaul operators. For example,MSOs are seeking to increase their value to the MNOs by providingalternative backhaul paths for communication between UEs, such as UE105, and the mobile core, such as mobile core 107. MSOs andsmall/independent wireless operators currently employ wireless devices,such as the small cell 103, for capturing a wireless data transmissionand passing it through a backhaul system, as shown in FIG. 1. In theembodiment of FIG. 1, the backhaul system includes modem 102, MTS 106,and meditator 109 and may additionally include an optional agent 104,which is discussed further below. The small cell 103 comprises many ofthe features of a larger base station such as the air-to-air interfaceand protocol handling. In some instances, the small cell 103 may be amulti-radio hotspot providing for WiFi, as well as LTE Licensed AssistedAccess (LTE-LAA) or LTE Unlicensed (LTE-U).

In an alternative embodiment communication is only WiFi communicationand is between a STA (not shown) a WiFi core (not shown). To modify thesystem of FIG. 1 to accommodate the WiFi embodiment the skilled artisanwould replace small cell 103 with a WiFi station (STA) and the mobilecore 107 with a WiFi core.

Small cells and similar wireless technologies (collectively discussedand represented herein as small cells) represent new opportunities forMNOs. These new small cells allow operators to access additionalspectrum, use existing spectrum more efficiently, and promote greaterdeployment flexibility, all at a lower cost. Small cells also reduceradio access network build-out and backhaul investment, while improvingthe end user experience by providing increased access to mobilenetworks. Additionally, because small cells are much smaller, they canreduce a base station's footprint and have less environmental impact(e.g., in terms of power consumption).

The MSOs and MNOs, evolving from different technologies, generallyemploy different communication protocols and offer little insight toeach other. For example, the MSOs may employ the DOCSIS protocol totransport data to and from a modem 102. The MNOs, on the other hand, mayemploy a variety of wireless protocols including EDGE (Enhanced Datarates for GSM Evolution), 2G, 3G, 4G, 5G, LTE, or the like. While an MTSand a modem may be able to transport the wireless service traffic of theUE and the mobile core, the MTS and the modem need not process the datatransmitted. Rather, the MTS and the modem simply route the trafficbetween the appropriate parties. In the example of FIG. 1, traffic isrouted between UE 105 and mobile core 107 via small cell 103, modem 102,and MTS 106.

This lack of insight by the backhaul system into the wireless system'sdata, and vice versa (e.g., LTE system into the DOCSIS system, and viceversa), causes the grant of a request to transmit data across thewireless service link 100 to occur in a serial manner. For example, whenthe small cell 103 provides a grant to the UE 105 to transfer data tothe small cell 103, the modem 102 and the MTS 106 are unaware that thesmall cell 103 has provided a grant for a data transfer from the UE 105.When the data arrives at the small cell 103 it is then forwarded to themodem 102. Only when the data arrives at the modem 102 from the smallcell 103 does the modem transmit a request to the MTS 106. Themodem-to-MTS grant alerts the MTS 106 that the modem 102 has data totransmit and requires resources to do so. The MTS 106 can then scheduleresources for the modem 106 and transmits that as a “grant” back to themodem 102. The data is then transferred from the modem 102 to the MTS106 and then forwarded on to the mobile core 107. This serial grantingof data transfers results in unnecessary latency to the overall datatransfer from UE 105 to mobile core 107.

In the case of high-priority data, such as voice data, the unnecessarylatency may result in the data being irrelevant by the time it reachesthe intended recipient. For example, the UE 105 transfers blocks of datarepresenting relatively small portions of a conversation. When some ofthe blocks of data are delayed, they may no longer be relevant to theconversation and are as such dropped. When this occurs regularly, thequality of the conversation and the user's quality of experience (QoS)are degraded significantly. Similar issues exist when non-voice data istransmitted across the network, such as video data (live or stored),security data, access and control over remotely located resources,machine-to-machine applications, etc.

In this embodiment, the modem 102 learns from the small cell 103 thatthe UE 105 has issued a scheduling request to transfer data to the smallcell 103. For example, the small cell 103 may be an eNodeB operable tocommunicate in an LTE network, or a WiFi Access Point (STA) operable tocommunicate in a WiFi network. The UE 105, when it needs to transferdata across the wireless service link 100, issues a scheduling request(SR) to the eNodeB. The eNodeB then determines when the UE 105 cantransfer data to the eNodeB and issues an uplink (UL) grant to the UE105. The UE 105 then transfers its data to the eNodeB such that theeNodeB can propagate it through the wireless service link 100 to themobile core 107 operated by an MNO for subsequent processing, routing,and the like.

When the UE 105 has data to transmit the preparation for thetransmission process can be a multistep process by itself. For example,if the UE 105 does not have a valid grant, the UE 105 issues an SR then,after receiving the grant, transfers a buffer status report (BSR) to theeNodeB indicating how much data it is requesting to be transferred. TheeNodeB then issues the subsequent grant indicating the actual amount ofdata that can be transmitted. Upon receiving the grant, the UE 105transfers its data to the eNodeB.

The small cell 103 informs the modem 102 of the SR just after the smallcell 103 receives it. In an embodiment, this is accomplished by thesmall cell 103 transmitting an out of band message to the modem 102 toindicate that the small cell 103 has received the SR. Alternatively oradditionally, a modem 102 that is configured with functionality to readthe SR may do so. The modem 102 may read the SR to learn, for example,that the UE 105 is requesting to transfer data to the small cell 103.For example, the modem 102 may be configured with and/or include aportion of an eNodeB such that it can detect and read the LTE protocol,and therefore the SR, from the UE 105.

In a separate embodiment, the agent 104 (e.g., formed in software,hardware, or a combination thereof) may exist between the small cell 103and the modem 102 (or as a part of the small cell 103 and/or the modem102). Agent 104 is configured to intercept the SR or generate a copy ofthe SR during its transit from the small cell 103 to the modem 102,unpacks the SR (or the copy), and transmits an out of band message tothe modem 102 pertaining to the data containing within the SR. Once themodem 102 learns of the SR from agent 104, the modem 102 can alert theMTS 106 that it will need to transfer data when the modem 102 receivesit from the UE 105 (e.g., through the small cell 103). Alternatively,the modem 102 simply forwards the SR in a manner similar to that of anyother received data. It is then up to the MTS 106 or Mediator 109 toprocess the SR.

Thus, while the UE 105 and the small cell 103 are negotiating thetransfer of data through the wireless service link 100, the modem 102and the MTS 106 can negotiate their transfer of data before the data ofthe UE 105 arrives at the modem 102. This allows the data transferscheduling and granting processes of the wireless service link 100 andthe backhaul communication link to occur in parallel or substantially inparallel.

Alternatively or additionally, an MTS may be configured withfunctionality of the mobile core 107. For example, in a DOCSIS protocolembodiment, the MTS 106 is a CMTS, and may include functionality of anLTE gateway that is operable to intercept a scheduling request from theUE 105 indicating that it needs to transfer data to the mobile core 107.This may direct the MTS 106 to initiate the establishment of acommunication session between the MTS 106 and the modem 102.

In another embodiment, the modem 102 and/or the MTS 106 may beconfigured to wait until the message is received from the small cell 103pertaining to the amount of data to be transferred from the UE 105. Forexample, when the small cell 103 receives an initial SR, the small cell103 understands that another detailed request will follow with a BSRrequesting a data transfer of a particular size. The small cell 103 willthen know when that data transfer will occur and how much data will besent. Accordingly, this information is then conveyed to the modem 102and/or the MTS 106 to initiate the granting through the backhaul'sprotocol based on when the actual data transfer will occur and the datasize.

Based on the foregoing, the UE 105 is any device, system, software, orcombination thereof operable to communicate wirelessly with a wirelessnetwork using any one or more wireless protocols including, 2G, 3G, 4G,5G, LTE, LTE-U, LTE-LAA, or the like, as well as with a WiFi networkusing any one or more wireless service protocols including 802.11ax.Examples of the UE 105 include, but are not limited to, laptopcomputers, tablet computers, and wireless telephones such as smartphones. The small cell 103 is any device, system, software, orcombination thereof operable to provide an air-to-air interface for themobile core 107, one example of which is a WiFi core. Examples of thesmall cell 103 include WiFi access points and base stations operating aseNodeBs in a wireless network. The modem 102 is any device, system,software, or combination thereof operable to provide data transfers withan MTS. Examples of the modem 102 include DOCSIS enabled set-top boxes.The MTS 106 is any device, system, software, or combination thereofoperable to communicate with the modem 102 as well as provide a wirelessservice session through the communication link provided by the modem 102and the MTS 106. Other exemplary embodiments are shown and describedbelow.

FIG. 2 is a flowchart illustrating an exemplary process 200 operablewith the modem 102 of the wireless service link 100 of FIG. 1. In thisembodiment, the modem 102 detects a message from a wireless service link100 indicating that the UE 105 has data to transmit to the mobile core107, in the process element 201. For example, the modem 102 may receivean out of band signaling message from the small cell 103 and/or unpackan SR received by the small cell 103 indicating that the UE 105 requestsa data transmission. Alternatively, the agent 104 may receive, interceptor generate a copy of an SR sent from the small cell 103 to the modem102, unpack the SR, and send an out of band signaling message to themodem 102 to alert the modem 102 of the scheduling request by the UE105.

From there, the modem 102 or the agent 104 may determine whether themessage is an SR or a BSR, in the process element 202. For example, ifthe UE 105 wishes to transmit its data to the small cell 103, the UE 105transmits an SR to the small cell 103 without indicating how much datait wishes to transmit. The UE 105 then receives a grant from the smallcell 103, which allows the UE 105 to respond to the small cell 103 withinformation regarding the amount of data it has to transmit. If thesmall cell 103 receives the initial SR, then the modem 102 instructs theMTS 106 that data from the UE 105 is pending, in the process element203. Such will alert the MTS 106 that the modem 102 will be requesting agrant through the communication link established between the modem 102and the MTS 106. The MTS 106 may further anticipate that the modem 102will send additional signaling messages, such as the BSR message or thegrant for the wireless service link 100 issued by the small cell 103, byissuing a grant for the modem 102 over the communication linkestablished between the modem 102 and the MTS 106. The BSR messageindicates the amount and the quality of service (QoS) requirement ofdata the UE 105 wishes to transfer to the small cell 103. The grant isgenerated by the small cell 103 for the UE 105 that indicates the amountof data the UE 105 is to transmit and the time of transmission. Knowingthe precise amount, the timing, and the QoS assignment of the expecteddata arrival at the small cell 103 helps the MTS 106 to determine thesize, timing, and the QoS assignment of the grant over the DOCSIScommunication link. This will also give the MTS 106 ample time toschedule a grant for the modem 102 to transfer data from the UE 105 tothe MTS 106 over the communication link.

If the message from the UE 105 is a BSR indicating the amount and theQoS requirement of data being transferred by the UE 105 or a grant thatis issued by the small cell 103 indicating the amount of data fortransmission, and expected time of data arrival at the small cell 103,then the modem 102 may request a data transfer to the MTS 106, in theprocess element 204. For example, the modem 102 may generate andtransmit a message to the MTS 106 requesting to transfer an amount ofdata from the UE 105 indicated by the BSR or as indicated by the grant.Alternatively, the modem 102 may simply encapsulate the BSR and/or thegrant message and transmit it to the MTS 106. The MTS 106, uponscheduling the data transfer from the modem 102, issues a grant grantingthe data transfer from the modem 102.

Once the grant by the MTS 106 has been issued, the modem 102 can simplyreceive the data from the UE 105 in the wireless service link 100, inthe process element 206, and transfer the data of the UE 105 to the MTS106 at its allocated time as indicated by the MAP grants, in the processelement 207. That is, requesting/granting of data transfers between themodem 102 and the MTS 106 is performed substantially in parallel withthe requesting/granting of data transfers between the UE 105 and thesmall cell 103, thereby reducing latency in the overall data transfer.

FIG. 3 is a flowchart illustrating an exemplary process 220 operablewith the MTS 106 of FIG. 1. In this embodiment, the MTS 106 receives andprocesses the request from the modem 102 to transfer data of the UE 105,in the process element 221. As mentioned, the request may includeinformation pertaining to the size and the QoS requirement of the datatransfer retrieved from a BSR issued by the UE 105 or informationpertaining to the size, and the precise time of the data transferretrieved from a grant issued by the small cell 103. Accordingly, theMTS 106 may determine the size, the QoS assignment, and the timing ofthe data transfer, either based on the BSR, the grant information, oranother internal process, in the process element 222, and schedule agrant of the data transfer. Once the data transfer has been scheduled,the MTS 106 transfers the grant to the modem 102, in the process element223. Then, when the modem 102 receives the data from the UE 105 throughthe small cell 103, the modem 102 can quickly transfer the data to theMTS 106 because the grant is issued substantially in parallel with thegrant by the small cell 103 to the UE 105.

The MTS 106 may store in memory the amount of data associated with thedata transfer (and optionally all previous UE data transfers), in theprocess element 224. For example, the MTS 106 may be operable to issueunsolicited data transfer grants through an unsolicited grant service(UGS) or some other unsolicited grant. When the MTS 106 has sparecapacity (i.e., the process element 225) the MTS 106 can transfer anunsolicited grant to the modem 102 without being requested to do so suchthat the modem 102 can transfer data (UE data and/or modem data) if ithas any without delay associated with a request-grant process. Byretaining the size value of the data associated with the previous UEdata transfers (and optionally all previous UE data transfers), the MTS106 can better estimate how much spare data transfer capacity can beissued through unsolicited grants and further decrease system latency.

In one illustration, UEs 105(1)-(4) (not shown) request data transfersto the small cell 103 at or about the same time. For example, UE 105(1)needs to transmit two bytes of data, UEs 105(2) and UEs 105(3) need totransmit four bytes of data each, and UE 105(4) needs to transmit sixbytes of data, thus totaling 16 bytes of data. The small cell 103 maycombine the data transfer information into a BSR for transmission to theMTS 106. The MTS 106 may use this information to generate subsequentunsolicited grant of 16 bytes of data such that all of the data from UEs105(1)-(4) may be transferred at or about the same time.

The MTS 106 may determine any type of typical unsolicited grant sizesfor the modem 102, as shown in process element 226. For example, the MTS106 may average the data sizes of BSRs from the small cell 103 overtime, may use data sizes of one or multiple UEs 105, may base the datasizes of the unsolicited grants on a time of day, or the like. In anycase, when the MTS 106 has spare capacity and determines a size of theunsolicited grant, the MTS 106 may transfer the unsolicited to the modem102, as in process element 227, such that the modem 102 can transferdata of the UE 105 that it receives from the small cell 103.

FIG. 4 is an exemplary communication diagram of the wireless servicelink 100 of FIG. 1. In this embodiment, the small cell 103 is an eNodeBoperable within an LTE network and employing LTE communicationprotocols. To the left of the UE 105 are timing diagrams exemplary ofthe LTE communication protocol. Timing as shown and discussed is notmeant to be limiting in anyway, but merely for illustrative purposes andto convey understanding. For example, after a data arrives at the UE,the UE 105 processes the data to determine an SR is needed. The UE 105waits for 5 ms for an SR opportunity then the UE 105 transfers the SR tothe eNodeB 103, which typically takes 1 ms. The eNodeB 103 processes theSR and generates a grant which typically takes between 2 and 4 ms beforeit sends a first UL grant to the UE 105, which again takes typically 1ms. Upon receipt of the first UL grant the UE 105 processes the grant,getting a BSR ready for transmission, which typically takes 4 ms, thentransmits uplink (UL) data, e.g., a BSR, back to the eNodeB 103, again a1 ms transmission. This UL data is generally just an indicator of theamount of UL data that is requested from the UE 105 when a second ULgrant from the eNodeB 103 is received. That is, the UE 105 transfers theBSR, which also acts as an SR, to the eNodeB 103 indicating how muchdata is to be expected in the next transfer to the eNodeB 103.

The eNodeB 103 process the BSR and generates a second UL grant for theUE 105 in 2 to 4 ms. The UE 105 processes the received second grant andprepares the data for transmission, which can take between 2 and 4 ms,then sends the data to the eNodeB 103.

Upon receiving the initial SR, the eNodeB 103 may, for example,communicate information about the SR to the modem 102 through out ofband signaling or transfer the SR to modem 102. If the SR is sent to themodem 102 the SR can be unpacked and modem 102 can determine that the UE105 has data to be transmitted across the wireless service link 100 andoptionally the type of data. In this regard, the modem 102 may request adata transfer from the MTS 106 such that the MTS 106 can beginscheduling for the data of the UE 105. The MTS 106 issues a MAP grant(or some other type of grant) to facilitate the further transfer of BSRand/or LTE grant from the modem 102.

When the eNodeB 103 receives the BSR, it may transfer the BSR in whole,information about the BSR, the actual LTE grant of the UE 105, or somecombination thereof, to the modem 102. The LTE grant issued by theeNodeB 103 provided information regarding the size and the precisetiming at which the UE 105 is scheduled to transmit its data. This,along with BSR, indicates to the modem 102 how much data, at what QoS isto be expected by the UE 105, and the precise time. The modem 102 thentransfers this information (e.g., the BSR, the LTE grant, or similar asdiscussed above) to the MTS 106. As the MTS 106 has been preparing forthe actual transfer of data from the UE 105, the MTS 106 can transfer adata transfer grant (e.g., a DOCSIS MAP in a cable network embodiment)to the modem 102. With the grant in hand, the modem 102 can simply waitfor the UL data from the UE 105 and the eNodeB 103 such that it may beimmediately forwarded to the MTS 106 through the communication link.Upon receipt of the data the MTS 106 then forwards it to the mobile core107.

Although shown or described in a particular form of messaging, theinvention is not intended to be limited to the exemplary embodiment. TheMTS may have a gateway configured therewith that is operable tointerpret LTE traffic. The modem 102 may simply wait until it receives aBSR and transfer it as part of the request for data transmission. TheMTS 106 may then issue the data transfer grant based on the BSR or theLTE grant info, and the information contained therein.

FIG. 5 is a block diagram of an exemplary buffer status report (BSR)operable with the wireless service link of FIG. 1. In LTE, the SR istypically a 1-bit indicator sent by UE 105 to request UL bandwidth. But,the SR alone is not sufficient for the eNodeB 103, that is, the eNodeB103 needs more information about a size of the data to be transmittedfrom UE 105 before it can provide a data grant to the UE 105. So, theeNodeB 103 simply sends a grant of sufficient size for the transmissionof the BSR from the UE 105 to the eNodeB 103.

As illustrated in FIG. 5, the BSR is this configured as a 3-byte MACcontrol element that reports outstanding data for each of UE 105's fourlogical channel groups. The mapping of a radio bearer (i.e., a logicalchannel) to a logical channel group (LCG) is done at the session setuptime by the eNodeB 103 based on the corresponding QoS attributes of theradio bearers (e.g., QoS Class Identifier (QCI), an Allocation andRetention Priority (ARP), a Guaranteed Bit Rate (GBR), a Maximum BitRate (MBR), an Access Point Name-Aggregate Maximum Bit Rate (APN-AMBR),a UE-AMBR, etc.). For example, radio resource control (RRC) messages mapto LCG0. The embodiments herein allow the LCG to be directly mapped tothe upstream service flow.

FIG. 6 is another exemplary communication diagram of the wirelessservice link 100 of FIG. 1. In this embodiment, data transfer grants bythe MTS 106 are based upon the BSRs from the UE 105. That is, the UE 105already has a valid LTE grant, without having to first send the SR. Thisallows the data requesting/granting to be further compacted and thusfurther reduces latency within the wireless service link 100. Forexample, the UE 105 issues a BSR to the eNodeB 103. In doing so, theeNodeB 103 transfers the BSR to the modem 102 along with the LTE grantsuch that the modem 102 knows that the eNodeB 103 will be granting thedata transfer to the UE 105. The eNodeB 103 then, or at substantiallythe same time as the BSR/LTE Grant is sent to the modem 102, transfersthe UL grant to the UE 105, such that it can transfer its UL data andoptionally another BSR (see below) to the eNodeB 103.

With the LTE grant and the BSR in hand, the modem 102 can request a datatransfer of the MTS 106 and indicate within that request how much datawill be transferred by the UE 105. The MTS 106 issues a grant to themodem 102 based on the amount of data, QoS requirement and precisetiming of the expected data transfer. When the UL data is received bythe eNodeB 103, it may be transferred by the modem 102 to the MTS 106.

However, when transmitting the UL data, the UE 105 may also include aBSR for its next transfer of data, as referenced above. The eNodeB, intransferring the UL data, also transfers the subsequent BSR and/or itsLTE grant info for the subsequent data transfer from the UE 105 to themodem 102. Thus, the modem 102 is able to request a subsequent datatransfer of the MTS 106 using the subsequent BSR and/or LTE grant info.The MTS 106 transfers the first UL data to the mobile core 107. Then,the MTS 106 issues a second grant to the modem 102 which then waits forthe second UL data from the UE 105.

When the eNodeB 103 issues the second UL grant to the UE 105, the UE 105responds in turn with the second UL data to the eNodeB 103. The eNodeB103 forwards this second UL data to the modem 102. As the modem 102already has its second grant for the second UL data, it immediatelytransfers the next UL data to the MTS 106, which in turn forwards thenext UL data to the mobile core 107.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. Embodiments utilizing network functionsvirtualization (NFV) and virtualized hardware, such as a virtualizedMTS, modem, etc., are also contemplated. In one embodiment, theinvention is implemented in whole or in part in software, which includesbut is not limited to firmware, resident software, microcode, etc. FIG.7 illustrates a computing system 300 in which a computer readable medium306 may provide instructions for performing any of the methods disclosedherein.

Furthermore, the invention can take the form of a computer programproduct accessible from the computer readable medium 306 providingprogram code for use by or in connection with a computer or anyinstruction execution system. For the purposes of this description, thecomputer readable medium 306 can be any apparatus that can tangiblystore the program for use by or in connection with the instructionexecution system, apparatus, or device, including the computer system300.

The medium 306 can be any tangible electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system (or apparatus ordevice). Examples of a computer readable medium 306 include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Some examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

The computing system 300, suitable for storing and/or executing programcode, can include one or more processors 302 coupled directly orindirectly to memory 308 through a system bus 310. The memory 308 caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode is retrieved from bulk storage during execution. Input/output orI/O devices 304 (including but not limited to keyboards, displays,pointing devices, etc.) can be coupled to the system either directly orthrough intervening I/O controllers. Network adapters may also becoupled to the system to enable the computing system 300 to becomecoupled to other data processing systems, such as through host systemsinterfaces 312, or remote printers or storage devices throughintervening private or public networks. Modems and Ethernet cards arejust a few of the currently available types of network adapters.

FIG. 8 is a block diagram of an exemplary system operable to providewireless service for a plurality of UEs 105-1-105-N (where “N” is simplyintended to represent an integer greater than “1” and not necessarilyequal to any other “N” reference designated herein). For example,upstream and downstream links of an exemplary communication systemoffers high speed data services over connected devices, such as themodem 102. The modem 102 may be configured with or receivecommunications from the small cell 103 so as to allow the UEs 105 tocommunicate through the communication system in a manner that istransparent to the user.

The communication system includes a communication component 401configured with an upstream hub 420. The hub 420 is coupled to a fibernode 421 via optical communication links 405 and 406. The hub 420includes a Modem Termination System (MTS) 106 an electrical to opticalconverter 403, and an optical to electrical converter 404. The node 421is similarly configured with an optical to electrical converter 408 andan electrical to optical converter 407.

The communication component 401 is the source for various communicationsignals. Antennas may receive communication signals that are convertedas necessary and transmitted over fiber optic cables 405 to the hub 420.Several hubs may be connected to a single communication component 401and the hub 420 may each be connected to several nodes 421 by fiberoptic cable links 405 and 406. The MTS 106 may be configured in thecommunication component 401 or in the hub 420.

Downstream, such as in homes/businesses, are devices that operate asdata terminals. These data terminals are modems. A modem can act as ahost for an Internet Protocol (IP) device such as personal computer.However, the modem can be configured with a small cell so as to providewireless services through the system for the UEs 105-1-105-N.

Transmissions from the MTS 106 to the modem are carried over thedownstream portion of the communication system generally in the bandbetween 54 MHz and 3 GHz, for example. Downstream digital transmissionsare continuous and are typically monitored by many modems. Upstreamtransmissions from the modems to the MTS 106 are, for example, typicallycarried in the 5-600 MHz frequency band, the upstream bandwidth beingshared by the Modems that are on-line. However, with greater demands fordata, additional frequency bands and bandwidths are continuously beingdeployed in the downstream and upstream paths. It is also possible thatModems and the MTS engage in full duplex transmission modes, wherebyconcurrent transmissions on the upstream and the downstream over thesame frequency is supported. Equivalent communications and protocols forfiber optic transmissions are also contemplated. For example using anoptical network terminal (ONT) or optical line termination (OLT), and anoptical network unit (ONU), and equivalent protocols such as EPON, RFOG,or GPON.

The MTS 106 connects the system to the Internet backbone. The MTS 106connects to the downstream path through an electrical to opticalconverter 404 that is connected to the fiber optic cable 406, which inturn, is connected to an optical to electrical converter 408 at the node421. The signal is transmitted to a diplexer 409 that combines theupstream and downstream signals onto a single cable. The diplexer 409allows the different frequency bands to be combined onto the same cable.The downstream channel width in the United States is generally 6megahertz to 192 MHz with the downstream signals being transmitted inthe 54 MHz to 3 GHz band. Upstream signals are presently transmittedbetween 5 and 600 MHz, but again other bands are being considered toprovide increased capacity.

After the downstream signal leaves the node 421, the signal is typicallycarried by a coaxial cable 430. At various stages, a power inserter 410may be used to power the coaxial line equipment, such as amplifiers orother equipment. The signal may be split with a splitter 411 to branchthe signal. Further, at various locations, bi-directional amplifiers 412may boost and even split the signal. Taps 413 along branches provideconnections to subscriber's homes 414 and businesses.

Upstream transmissions from subscribers to the hub 420/headend 401 occurby passing through the same coaxial cable 430 as the downstream signals,in the opposite direction on a different frequency band. The upstreamsignals are sent typically utilizing Quadrature Amplitude Modulation(QAM) with forward error correction. The upstream signals can employQPSK or any level of QAM, including 8 QAM, 32 QAM, 64 QAM, 128 QAM, 256QAM, 512 QAM, 1024 QAM, and 4096 QAM. Modulation techniques such asSynchronous Code Division Multiple Access (S-CDMA) and OrthogonalFrequency Division Multiple Access (OFDMA) can also be used. Of course,any type of modulation technique can be used, as desired.

Upstream transmissions, in this embodiment, can be sent in afrequency/time division multiplexing access (FDMA/TDMA) scheme. Thediplexer 409 splits the lower frequency signals from the higherfrequency signals so that the lower frequency, upstream signals can beapplied to the electrical to optical converter 407 in the upstream path.The electrical to optical converter 407 converts the upstream electricalsignals to light waves which are sent through fiber optic cable 405 andreceived by optical to electrical converter 403 in the node 420. Thefiber optic links 405 and 406 are typically driven by laser diodes, suchas Fabry Perot and distributed feedback laser diodes. Laser diodes beginto “lase” at a certain diode threshold current.

FIG. 9 is an exemplary communication diagram of the wireless servicelink employing WiFi. In FIG. 9, the communication diagram is illustratedas part of a WiFi system that provides latency reduction in wirelessservice. In this regard, the communication link established between themodem 102 and the MTS 106 interfaces with a WiFi core 501 as well as anaccess point (AP) 502 (e.g., wireless access point or “WAP”). The AP 502communicates with a WiFi station (STA) 503 such that the STA 503 cantransmit data to the WiFi core 501.

The STA 503 issues a “request to send” to the AP 502 when the STA 503needs to transmit data to the WiFi core 501. The AP 502 transfers arequest to the modem 102 asking the modem 102 if the AP 502 can transferthe data of the STA 503. When the AP 502 determines that the STA 503 cantransfer its data, the AP 502 transfers a “clear to send” to the STA503. During this time, the modem 102 issues a request to transfer datato the MTS 106. And, the MTS 106 issues a MAP (or some other grantingmechanism) to the modem 102 allowing the modem 102 to transfer the dataof the STA 503.

From there, the modem 102 waits for the data from the AP 502. When theSTA 503 transfers its data to the AP 502, the AP 502 transfers itdirectly to the modem 102 such that the modem 102 can transfer the dataof the STA 503 through the communication link established between themodem 102 and the MTS 106. Once the MTS 106 receives the data of the STA503, the MTS 106 transfers a data of the STA 503 to the WiFi core 501.

FIG. 10 is a block diagram of an exemplary communication link comprisinga virtualized Modem Termination System (vMTS) 1062, a remote PHY device(RPD) 1082, and a modem 1022. The communication link is coupled with avirtualized wireless link (e.g., configured from a remote small cell(rSC) 1032 and a central small cell (cSC) 1072 described in greaterdetail below). It will be understood that a mediator 1092 may beintegrated with or communicatively coupled with vMTS 1062. The vMTS 1026may be, for example, a CMTS, a Fiber Node, a Fiber Hub, an optical linetermination (OLT), or other termination device. Mediator 1092 may beimplemented, for example, as a software agent in any of such devices. Ifmediator 1092 is integrated with a vMTS, integration may be via softwareor hardware. Mediator 1092 is operable to generate a backhaul grant (anexample of which is shown as MAP/unsolicited grant in FIG. 14) for modem1022 in response to a message to cSC 1072. The backhaul grant istransmitted close in time to the UL grant sent from cSC 1072 to UE 1052such that modem 1022, which receives the backhaul grant, can prepareresources to backhaul the UE data at substantially the same time as theUE 1052 prepares and transmits the data to the modem 1022. Thissubstantially parallel processing by the UE 1052 and the modem 1022prepares the modem 1022 to backhaul the data when it arrives.

In alternative embodiments, mediator 1092 may be situated between vMTS1062 and cSC 1072 or configured with or otherwise in communication withcSC 1072 such that mediator 1092 generates a backhaul grant in responseto one or more of the BRS (or one or more wireless grants), an out ofband message comprising UL grant information such as a UL grant summary(see FIG. 14), or the UL grant itself. As suggested above, mediator 1092may be implemented as software or hardware, and may be formed withinvMTS 1062 or cSC 1072, as a standalone device placed in thecommunication line between the vMTS 1062 and the cSC 1072, or as acomponent of the vMTS 1062 or the cSC 1072.

In an embodiment, one of vMTS 1062 and mediator 1092 generates one ormore backhaul grants in response to one or more of the BSRs, one or morePHY Translated Messages (PTM) (see FIG. 14), or one or more wirelessgrants. In a related embodiment, the number of generated backhaul grantsis fewer than the number of BSRs, PTMs, or wireless grants, and may beas few as one backhaul grant or as many as one less than the number ofBSRs, PTMs, or wireless grants. In these and other embodiments, the vMTSor mediator 1092 aggregates the received BSRs, PTMs, or wireless grantsto generate the one or more backhaul grant.

The UE 1052 may wirelessly communicate with other UEs (not shown) in awireless service network for the purpose of transmitting and/orreceiving data. A cSC 1072 (e.g., control portion of a virtualizedwireless link) controls the operations of the UE 1052 within thewireless network. This includes, among other things, managingsubscription information (e.g., data communication, data plans, roaming,international calling, etc.) and participating in processes that ensurethat the UE 1052 can place calls and transmit data within the wirelessnetwork. Mediator 1092 cooperates with the vMTS to providecommunications between the UE 1052 and the cSC 107 such that the cSC1072 can control the operations of the UE 1052, for example, when the UE1052 is within range of a “small cell,” such as rSC 1032.

In the past, MNOs often maintained, operated, and controlled wirelessbase stations themselves for the purposes of providing communicationswith UEs. For example, an MNO employing LTE communications may operate aplurality of base stations in an area to provide wireless services tosubscribing UEs in that area.

Now MSOs are capable of acting as backhaul operators. For example, MSOsmay engage with MNOs for the purpose of providing alternative backhaulpaths for communication between UEs, such as UE 1052, and the mobilecore (not shown). MSOs and small/independent wireless operatorscurrently employ wireless devices, such as the rSC 1032, for capturing awireless data transmission and passing it through a backhaul system, asshown in FIG. 10. In the embodiment of FIG. 10, the backhaul systemincludes modem 1022, a RPD 1082, vMTS 1062, and meditator 1092. The rSC1032 comprises many of the features of a larger base station such as theair-to-air interface 1102 and protocol handling. In some instances, therSC 1032 may be a multi-radio hotspot providing for WiFi, as well as LTELicensed Assisted Access (LTE-LAA) or LTE Unlicensed (LTE-U).

In an alternative embodiment wireless communication is WiFicommunication and is between a STA (not shown) or a WiFi core (notshown). To modify the system of FIG. 10 to accommodate the WiFiembodiment the skilled artisan would replace UE 1052 with a WiFi station(STA), rSC 1032 with a Wi-Fi transceiver and relevant electronics, andthe cSC 107 with a virtualized WiFi controller configured with orotherwise in communication with the Wi-Fi core.

Small cells and similar wireless technologies (collectively discussedand represented herein as small cells) represent new opportunities forMNOs. These new small cells allow operators to access additionalspectrum, use existing spectrum more efficiently, and promote greaterdeployment flexibility, all at a lower cost. Small cells also reduceradio access network build-out and backhaul investment, while improvingthe end user experience by providing increased access to mobilenetworks. Additionally, because small cells are much smaller, they canreduce a base station's footprint and have less environmental impact(e.g., in terms of power consumption).

The MSOs and MNOs, evolving from different technologies, generallyemploy different communication protocols and offer little insight toeach other. For example, the MSOs may employ the DOCSIS protocol totransport data to and from a modem 1022. The MNOs, on the other hand,may employ a variety of wireless protocols including EDGE (Enhanced Datarates for GSM Evolution), 2G, 3G, 4G, 5G, LTE, or the like. While thevMTS 1062 and the modem 1022 may be able to transport the wirelessservice traffic of the UE 1052, the vMTS 1062 and the modem 1022 neednot process the data transmitted. Rather, the vMTS 1062 and the modem1022 simply route the traffic between the appropriate parties. In theexample of FIG. 10, traffic is routed between UE 1052 and cSC 1072 viarSC 1032, modem 1022, RPD 1082, and vMTS 1062.

This lack of insight by the backhaul system into the wireless system'sdata, and vice versa (e.g., LTE system into the DOCSIS system, and viceversa), previously caused the request to transmit data across thecommunication link to occur in a serial manner. For example, when therSC 1032 provided a grant to the UE 1052 to transfer data to the rSC1032, the modem 1022 and the vMTS 1062 were unaware that the rSC 1032has provided a grant for a data transfer from the UE 1052. When the dataarrived at the rSC 1032, it was then forwarded to the modem 1022. Onlywhen the data arrives at the modem 102 from the rSC 1032 did the modemtransmit a request to transmit the data to the vMTS 1062. Themodem-to-MTS grant alerts the vMTS 1062 that the modem 1022 has data totransmit and requires resources to do so. The vMTS 1062 could thenschedule resources for the modem 1022 and transmit a grant back to themodem 1022. The data would then be transferred from the modem 1022 tothe vMTS 1062 and then forwarded on to the cSC 1072. This process ofserial granting data transfers results in unnecessary latency.

In the case of high-priority data, such as voice data, the unnecessarylatency may result in the data being irrelevant by the time it reachesthe intended recipient. For example, the UE 1052 transfers blocks ofdata representing relatively small portions of a conversation. When someof the blocks of data are delayed, they may no longer be relevant to theconversation and are as such dropped. When this occurs regularly, thequality of the conversation and the user's quality of experience (QoS)are degraded significantly. Similar issues exist when non-voice data istransmitted across the network, such as signaling traffic, video data(live or stored), security data, access and control over remotelylocated resources, machine-to-machine applications, etc.

In one embodiment, the UE 1052 has issued a scheduling request totransfer data to the cSC 1072. For example, the rSC 1032 may be awireless transceiver portion of an eNodeB operable to communicate in anLTE network, or a wireless transceiver portion of a Wi-Fi Access Point(AP) operable to communicate in a WiFi network. The UE 1052 (or Wi-FiSTA), when it needs to transfer data, issues a scheduling request (SR)to the cSC 1072. The cSC 1072 then determines when the UE 1052 cantransfer data to the cSC 1072 and issues an uplink (UL) grant to the UE1052. The UE 1052 then transfers its data to the cSC 1072 for subsequentprocessing, routing, and the like.

When the UE 1052 has data to transmit the preparation for thetransmission process can be a multistep process by itself. For example,if the UE 1052 does not have a valid grant, the UE 1052 issues an SRthen, after receiving the grant, transfers a bandwidth request message,in the present embodiment called a buffer status report (BSR), to thesmall cell indicating how much data it is requesting to be transferred.The small cell then issues the subsequent grant indicating the actualamount of data that can be transmitted. Upon receiving the grant, the UE1052 transfers its data to the small cell.

To illustrate, the SR may be a 1 bit indicator that the PHY layer (e.g.,in the rSC 1032) can decode. The rSC 1032 may then forward a PHYtranslated message based on the SR to the cSC 1072 via the communicationlink. The PHY translated message is then transmitted to the modem 1022,which generates a DOCSIS request message (REQ) to request resources toaccommodate the forth coming BSR on the backhaul system. The vMTS 1062may then generate a grant that is large enough to accommodate the BSR.

As mentioned, the communication link may be configured from at least thevMTS 1062 and the modem 1022 and the communication link is coupled witha virtualized wireless link. The components of the communication link,as well as the components of the virtualized wireless link, may bevirtualized. For example, the components of FIGS. 11A and 11B illustrateblock diagrams of protocol stack layers of a virtualized wireless links,shown in FIG. 11A as a vBS protocol stack 1302A in an LTE networkembodiment and shown in FIG. 11B as a vBS protocol stack 1302B in an LTEnetwork embodiment. FIGS. 12A and 12B illustrates block diagrams of MTSprotocol stack layers 1312A and 1312B. The vBS protocol stack 1302A and1302B comprise a plurality of protocol layers including a Packet DataConvergence Protocol (PDCP) 1202, Radio Link Control (RLC) 1212, anupper MAC layer 1222, a lower MAC layer 1232, and a physical interface(PHY) 1242. FIG. 11A differs from FIG. 11B in that PDCP 1202, RLC 1212,and upper MAC Layer 1222 are situated with cSC 1072A and lower MAC layer1232 and PHY 1242 are situated in rSC 1032A in vBS protocol stack 1302Awhile PDCP 1202, RLC 1212, upper MAC Layer 1222, and lower MAC layer1232 are situated with cSC 1072B and PHY 1242 is situated in rSC 1032Bin vBS protocol stack 1302B. The MTS protocol stacks 1312A and 1312Bcomprise a plurality of layers including the IP layer 1252, the MAClayer 1262, and the PHY 1272. FIG. 12A differs from FIG. 12B in that IPlayer 1252 and the MAC layer 1262 are situated with vMTS 1062A and thePHY 1272A is situated with RPD 1082A in MTS protocol stack layers 1312Awhile IP layer 1252 is situated with vMTS 1062B and the MAC layer 1262and the PHY 1272A are situated with RMPD 1082B in MTS protocol stacklayers 1312B. It will be understood that all embodiments discussedherein are directed to embodiments utilizing vBS protocol stack 1302Aand MTS protocol stack 1312A, but embodiments utilizing vBS protocolstack 1302B and MTS protocol stack 1312B are also contemplated and onlyrequire only minor modifications, which are well within the ability ofthe skilled artisan after reading the present disclosure.

In an embodiment, mediator 1092 is situated between a remote MAC/PHYdevice and a vMTS, such as between RMPD 1082B and vMTS 1062B, as shownin FIG. 12B.

Utilizing MTS protocol stack layers 1312B provides for an additionallocation mediator 1092 may be employed, namely between RMPD 1082B andvMTS 106B, which is not shown but is contemplated.

Functionality of the MTS 1312 may also be virtualized. For example, thePHY 1272 of the MTS 1312 may be implemented as a Remote PHY Device, suchas RPD 1082 which has little to no intelligence, while the remainingcore of the MTS 1312 (i.e., the IP 1252 and the MAC 1262) may bevirtualized into a separate component, i.e., the vMTS 1062.

In a separate embodiment, RPD 1082 is replaced by a remote device (RD),not shown. RD is configured to implement the PHY layer and the MAClayer, similar to PHY 1272 and MAC 1262, respectively. In thisembodiment IP 1252 remains within vMTS 1062.

In whatever configuration, the virtualized wireless link comprises therSC 1032, and the cSC 1072.

In one embodiment, the SR is intercepted (or a copy is generated) duringits transit from the rSC 1032 to the modem 1022. From there, the SR (orthe copy) is unpacked and transmitted as an out of band message to themodem 1022. Once the modem 1022 learns of the SR, the modem 1022 canalert the vMTS 106 that it will need to transfer data when the modem1022 receives it from the UE 105 (e.g., through the rSC 1032).Alternatively, the modem 1022 forwards the SR in a manner similar tothat of any other received data. It is then up to the vMTS 1062 ormediator 1092 to process the SR.

Based on the foregoing, the UE 1052 is any device, system, software, orcombination thereof operable to wirelessly communicate with a wirelessservice network using any one or more wireless protocols including, 2G,3G, 4G, LTE, LTE-U, LTE-LAA, or the like, as well as with a WiFi networkusing any one or more wireless service protocols including 802.11ax.Examples of the UE 1052 include laptop computers, tablet computers, andcellular telephones, such as smart phones. The rSC 1032 is any device,system, software, or combination thereof operable to provide anair-to-air interface 1102 for communication with the UE 1052. Examplesof the rSC 103 include WiFi access points and base stations, such aseNodeBs, operating as or part of a vBS in a wireless service network.The modem 1022 is any device, system, software, or combination thereofoperable to provide data transfers with a MTS. Examples of the modem1022 include but are not limited to a DOCSIS enabled set-top box, anOptical Network Unit or fiber optic modem, and a satellite modem.

The vMTS 1062 is any device, system, software, or combination thereofoperable to communicate with the modem 1022 as well as to facilitate thetransmission of wireless session data through the communication link.The cSC 1072 is any device, system, software, or combination thereofoperable to provide higher layer wireless communication functionalityand is in communication with a mobile core or mobile network (notshown). It will be understood that the control portion of thevirtualized wireless link is located within or its functionality isconfigured within cSC 1072, but for simplicities sake the cSC 1072 isgenerally referred to herein as the control portion of the virtualizedwireless link. However, the control portion of the virtualized wirelesslink may be implemented with fewer or more protocol layers shown in FIG.11. Other exemplary embodiments are shown and described below.

FIG. 13 is a flowchart illustrating an exemplary process 2002 operablewith the components of FIG. 10. In this embodiment, the UE 1052 has datato transmit to a mobile core (not shown) through the communication link.In this regard, the UE 1052 transfers a BSR through the communicationlink to a control portion of the virtualized wireless link (e.g.,residing with the cSC 1072), in the process element 2012. In an LTEexample of process element 2012, before the UE 1025 can transmit itsdata, the UE 1052 first issues a scheduling request (SR) to the rSC1032. The rSC 1032 transfers the SR to the modem 1022 which forwards itthrough the communication link to the vMTS 1062 and ultimately to thecSC 1072, which grants permission for the UE 105 to transmit a BSR.

When UE 1052 receives the cSC 1072 issued grant, the UE 1052 transmitsthe BSR indicating how much data it has in its buffer and informs thecSC 1072 accordingly. Thus, when the cSC 1072 receives and processes theBSR, it determines what resources are needed by the UE 1052 fortransmission. After processing of the BSR by the cSC 1072, the cSC 1072ascertains the details of what the UE 1052 has to transmit. The cSC 1072(or possibly the vMTS 1062), decides and then instructs the UE 1052 asto what will be transmitted. The cSC 1072 generates a wireless grant(e.g., an LTE grant) for the UE to transfer an amount of data on thevirtualized wireless link and signals or otherwise provides processabledata to the vMTS 1062A or 1062B of the MTS protocol stack 1312A, 1312B,which generates a backhaul grant for the modem 1022 to forward theamount of data from UE 1052 on the communication link, in the processelement 2022. Alternatively or additionally, the vMTS 1062A or 1062B maycomprise the functionality of the cSC 107 such that it may process theBSR to determine what the UE 1052 will transmit. Alternatively oradditionally, the mediator 109 may reside between the vMTS 1062A or1062B and the cSC 1072A or 1072 B (e.g., software, hardware, or acombination thereof) and may be enabled to unpack the LTE grantgenerated by the cSC 1072A or 1072B for processing and generating, forexample, as an out of band message to the vMTS 1062A or 1062B. The outof band message provides information to the vMTS 1062A or 1062B so thatit may generate a backhaul grant for transmission to the modem 1022.

In any case, the cSC 1072 generates the wireless grant based on the BSR,in the process element 2032. Since the cSC 1072 or the mediator 1092 isoperable to inform the vMTS 1062 of the amount of data that is to betransmitted by the UE 1052 as well as the precise timing of the datatransmission by the UE 1052, which has all been captured in the out ofband message, the vMTS 1062 can issue a backhaul grant for the UE 105 totransfer its data at or about the same time the vMTS 1062 receives theLTE grant generated by the cSC 1072. This substantially simultaneoustransmission of LTE and backhaul grants through the communication linkgreatly diminishes the latency involved with existing systems andmethods.

FIG. 14 is an exemplary communication diagram of the components of FIG.10. An SR-BSR process and a BSR-UL Data process are described. TheSR-BSR process, which covers from the transmission of the SR from the UE1052 to the receipt of the BSR Grant by the UE 1052, instructs the cSC1072 that UE 1052 requires resources for the transmission of a BSRthereby satisfying the scheduling request (SR). The BSR-UL Data process,which covers from the transmission of the BSR by the UE 1052 to thereceipt of the UL Data at the cSC 1072, satisfies the BSR, which is arequest to transmit UL data. An exemplary SR-BSR process is describedfirst, followed by an exemplary BSR-UL Data process.

The UE 1052 transmits a scheduling request (SR) to rSC 1032. The PHY1242 (see FIG. 11) of the rSC 1032 processes the SR and generates a PHYtranslated message (PTM), which is sent to the modem 1022. In responseto receiving the PTM, the modem 1022 generates and transmits a requestfor resources (REQ) to the vMTS 1062 via the RPD 1082A or RMPD 1082B (ora remote device (RD) as described above) such that modem 1022 maytransmit the PTM to the vMTS 1062 and cSC 1072. Upon receipt of the REQthe vMTS 1062 generates and transmits a MAP to the modem 1022 via RPD1082 such that modem 1022 may transmit the PTM to the vMTS 1062. Uponreceipt of the MAP, the modem 102 transmits the PTM to the cSC 107 viaRPD 108 and vMTS 1062. The cSC 1072 processes the PTM to issue a ULGrant back to the UE 105 and, optionally, an out of band message (OBM)to the vMTS 1062 which preemptively generates a MAP for the forthcomingBSR. The MAP for the BSR is then transmitted to the modem 1022, suchthat upon receipt of the BSR the modem 1022 is prepared to immediatelyforward the BSR to the cSC 1072. Alternatively an OBM is not utilizedand the vMTS 1062, upon receipt of the BSR grant, generates a BSR MAP,which is sent to modem 1022 and utilized in the same manner as describedabove. Alternatively, the vMTS 1062A periodically polls the modem 1022to see if the modem 1022 has SR or BSRs to transmit. Stillalternatively, the vMTS 1062A provides to the modem 1022 periodic, smallamount of grants sufficient to send one or multiple BSRs. In eithercase, the periodicity can be for example every 1 ms or longer. The grantsize can be adapted according to the number of BSRs have beenhistorically received in 1 ms time intervals. Based on the foregoing,BSRs can be forwarded immediately to the cSC 1072A by the modem 1022.Similar functionality exists within and between vMTS 1062B and cSC1072B, with only minor modifications that would be apparent to theskilled artisan after reading the present disclosure.

In this embodiment, the UE 1052 has data to transmit, and as such, itissues a BSR to the rSC 1032. The rSC 1032 transfers the BSR to themodem 1022 which propagates it to the RPD 1082. The RPD 1082 prioritizesor is instructed to prioritize the transfer of BSR among other trafficit receives and then transfers the BSR to the vMTS 1062 and ultimatelyto the cSC 1072, which generates a grant of all or a portion of the UE1052's UL data. In an embodiment, upon receiving the BSR, the cSC 1072provides the vMTS 1062 (e.g., via an out of band signaling message) withdata regarding the UL data grant, for example, with a UL Grant summary.The UL Grant summary may contain data pertaining to when and how much ofthe UL data from the UE 1052 was granted. This provides the vMTS 1062with the data it requires to perform its scheduling and to generate abackhaul grant (e.g., a DOCSIS MAP or some other granting mechanism) forthe UL data from the UE 1052. As described above, the backhaul grant issent from the vMTS 1062 to modem 1022, shown in FIG. 14 asMAP/unsolicited grant.

Thus, when the vMTS 1062 receives the UL grant summary from the cSC1072, the vMTS 1062 is operable to process it and generate the backhaulgrant transmission to the modem 1022 at or about the same time as thevMTS 1062 transmits the UL grant (e.g., the wireless grant, also calleda UL data grant herein) for the UL data of the UE 1052. The UL datagrant and the backhaul grant propagate through the communication linkuntil they reach their intended destinations. The RPD 1082 prioritizesor is instructed to prioritize the transfer of the UL data grant and thebackhaul grant among other traffic it receives. For example, when thebackhaul grant reaches the modem 1022, the modem 1022 is ready for theUL data from the UE 1052. And, when the UL grant reaches the UE 1052,the UE 1052 transfers its UL data to the rSC 1032 at its allocated time.Since the modem 1022 already has the backhaul grant, the modem 1022 cantransmit the UL data from the UE 1052 at its allocated time, which maybe as soon as it receives it from the rSC 1032.

Moreover, as the rSC 1032 may be communicating with a plurality of UEs1052, the rSC 1032 may collect a plurality of BSRs from the UEs 105 andforward those to the modem 1022. The modem 1022 may transmit those tothe vMTS 1062 which forwards them to the cSC 1072. In an out of bandmessage, the cSC 1072 may summarize the amount of data of the UL grantsthat are to be issued to the plurality of UEs 1052. With thisinformation, the vMTS 1062 can also provide unsolicited grants to themodem 1022 when capacity is available. But, the vMTS 1062 may do so withthe knowledge that is not supplying too much granted capacity.

For example, the vMTS 1062 may be operable to issue unsolicited grant tothe modem 1022 such that it may transfer data without requesting. ThevMTS 1062 may retain size values of the BSRs, such that when the vMTS1062 has spare capacity, the vMTS 1062 can better estimate how muchspare data transfer capacity the modem 1022 might need in response to ULgrants of the UEs 1052.

To illustrate, the vMTS 1062 may store in memory the amount of dataassociated with the data transfer (and optionally all previous UE datatransfers). The vMTS 1062 may then be operable to issue unsolicited datatransfer grants through an unsolicited grant or some other unsolicitedgrant based on that information. When the vMTS 1062 has spare capacity,the vMTS 1062 can transfer an unsolicited grant to the modem 1022without being requested to do so such that the modem 1022 can transferdata (UE data and/or modem data) if it has any without delay associatedwith a request-grant process. By retaining the size value of the dataassociated with the previous UE data transfers (and optionally allprevious UE data transfers), the vMTS 1062 can better estimate how muchspare data transfer capacity can be issued through unsolicited grantsand further decrease system latency.

In one illustration, UEs 1052(1)-(4) (not shown) request data transfersto the rSC 1032 at or about the same time. For example, UE 1052(1) needsto transmit two bytes of data, UEs 1052(2) and UEs 1052(3) need totransmit four bytes of data each, and UE 1052(4) needs to transmit sixbytes of data, thus totaling 16 bytes of data. The rSC 1032 may combinethe data transfer information into a BSR for transmission to the vMTS1062. The vMTS 1062 may use this information to generate subsequentunsolicited grant of 16 bytes of data such that all of the data from UEs1052(1)-(4) may be transferred at substantially reduced latency.

The vMTS 1062 may determine any type of typical unsolicited grant sizesfor the modem 1022. For example, the vMTS 1062 may average the datasizes of BSRs from the rSC 1032 over time, may use data sizes of one ormultiple UEs 105, may base the data sizes of the unsolicited grants on atime of day, or the like. In any case, when the vMTS 1062 has sparecapacity and determines a size of the unsolicited grant, the vMTS 1062may transfer the unsolicited to the modem 1022, such that the modem 1022can transfer data of the UE 1052 that it receives from the rSC 1032.

Although shown or described in a particular form of messaging, theinvention is not intended to be limited to the exemplary embodiment.

FIG. 15 is a block diagram of an exemplary buffer status report (BSR)operable with the components of FIG. 10. As mentioned, in LTE, the SR istypically a 1-bit indicator sent by UE 1052 to request UL bandwidth.But, the SR alone is not sufficient for a vBS. Rather, the vBS needsmore information about a size of the data before it can grant a datatransfer to the UE 105. So, the UE 1052 transmits a BSR. A media accesscontrol (MAC) scheduler generally assigns UL resources based on the BSR.So, the cSC 1072 sends a grant of sufficient size for the BSR.

As illustrated in FIG. 14, the BSR is configured as a 4-byte MAC controlelement that reports outstanding data for each of UE 1052's four logicalchannel groups. The mapping of a radio bearer (i.e., a logical channel)to a logical channel group (LCG) is done at the session setup time byrSC 1032 based on the corresponding Quality of Service (QoS) attributesof the radio bearers (e.g., QoS Class Identifier (QCI), an Allocationand Retention Priority (ARP), a Guaranteed Bit Rate (GBR), a Maximum BitRate (MBR), an Access Point Name-Aggregate Maximum Bit Rate (APN-AMBR),a UE-AMBR, etc.). For example, radio resource control (RRC) messages mapto LCG0. The embodiments herein allow the LCG to be directly mapped to aDOCSIS upstream service flow.

The BSR message is also operable to indicate the amount and the QoSrequirement of the data that the UE 1052 wishes to transfer to the rSC1032. The LTE grant is generated by the rSC 1032 for the UE 1052 andindicates the amount of data the UE 1052 is to transmit, the time oftransmission, and the QoS assignment of the data. Knowing the preciseamount, the timing, and the QoS assignment of the expected data arrivalat the rSC 1032 helps the vMTS 1062 to determine the size, timing, andthe QoS assignment of the grant over the communication link. This willalso give the vMTS 1062 ample time to schedule a grant for the modem1022 to transfer data from the UE 1052 to the vMTS 1062 over thecommunication link.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In one embodiment, the invention is implementedin software, which includes but is not limited to firmware, residentsoftware, microcode, etc. FIG. 16 illustrates a computing system 3002 inwhich a computer readable medium 3062 may provide instructions forperforming any of the methods disclosed herein.

Furthermore, the invention can take the form of a computer programproduct accessible from the computer readable medium 3062 providingprogram code for use by or in connection with a computer or anyinstruction execution system. For the purposes of this description, thecomputer readable medium 3062 can be any apparatus that can tangiblystore the program for use by or in connection with the instructionexecution system, apparatus, or device, including the computer system3002.

The medium 3062 can be any tangible electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system (or apparatus ordevice). Examples of a computer readable medium 3062 include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Some examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

The computing system 3002, suitable for storing and/or executing programcode, can include one or more processors 3022 coupled directly orindirectly to memory 3082 through a system bus 3102. The memory 3082 caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode is retrieved from bulk storage during execution. Input/output orI/O devices 3042 (including but not limited to keyboards, displays,pointing devices, etc.) can be coupled to the system either directly orthrough intervening I/O controllers. Network adapters may also becoupled to the system to enable the computing system 3002 to becomecoupled to other data processing systems, such as through host systemsinterfaces 3122, or remote printers or storage devices throughintervening private or public networks. Modems and Ethernet cards arejust a few of the currently available types of network adapters.

FIG. 17 is a block diagram of an exemplary system operable to providewireless service for a plurality of UEs 1052-1-1052-N (where “N” issimply intended to represent an integer greater than “1” and notnecessarily equal to any other “N” reference designated herein). Forexample, upstream and downstream links of an exemplary communicationsystem offers high speed data services over connected devices, such asthe modem 1022. The modem 1022 may be configured with or receivecommunications from the rSC 1032 so as to allow the UEs 1052 tocommunicate through the communication system in a manner that istransparent to the user.

The communication system includes a communication component 4012configured with an upstream hub 4202. The hub 4202 is coupled to a fibernode 4212 via optical communication links 4052 and 4062. The hub 4202includes a Modem Termination System (MTS) 1062 an electrical to opticalconverter 403, and an optical to electrical converter 4042. The node4212 is similarly configured with an optical to electrical converter4082 and an electrical to optical converter 4072.

The communication component 4012 is the source for various communicationsignals. Antennas may receive communication signals that are convertedas necessary and transmitted over fiber optic cables 4052 to the hub4202. Several hubs may be connected to a single communication component401 and the hub 4202 may each be connected to several nodes 4212 byfiber optic cable links 4052 and 4062. The vMTS 1062 may be configuredin the communication component 4012 or in the hub 4202.

Downstream, such as in homes/businesses, are devices that operate asdata terminals, such as modem 1022. For example, a modem can act as ahost for an Internet Protocol (IP) device such as personal computer.However, the modem can be configured with a small cell so as to providewireless services through the system for the UEs 105-1-105-N.

In this embodiment, transmissions from the vMTS 1062 to the modem arecarried over the downstream portion of the communication systemgenerally in the band between 54 MHz and 3 GHz. Downstream digitaltransmissions are continuous and are typically monitored by many modems.Upstream transmissions from the modems to the vMTS 1062 are, forexample, typically carried in the 5-600 MHz frequency band, the upstreambandwidth being shared by the Modems that are on-line. However, withgreater demands for data, additional frequency bands and bandwidths arecontinuously being deployed in the downstream and upstream paths. It isalso possible that modems and the MTS engage in full duplex transmissionmodes, whereby concurrent transmissions on the upstream and thedownstream over the same frequency are supported. Equivalentcommunications and protocols for fiber optic transmissions are alsocontemplated, for example, using an optical network terminal (ONT) oroptical line termination (OLT), and an optical network unit (ONU), andequivalent protocols such as EPON, RFOG, or GPON.

The vMTS 1062 connects the system to the Internet backbone. The vMTS 106connects to the downstream path through an electrical to opticalconverter 4042 that is connected to the fiber optic cable 4062, which inturn, is connected to an optical to electrical converter 4082 at thenode 4212. The signal is transmitted to a diplexer 4092 that combinesthe upstream and downstream signals onto a single cable. The diplexer409 allows the different frequency bands to be combined onto the samecable.

After the downstream signal leaves the node 4212, the signal is may becarried by a coaxial cable 4302. At various stages, a power inserter4102 may be used to power the coaxial line equipment, such as amplifiersor other equipment. The signal may be split with a splitter 4112 tobranch the signal. Further, at various locations, bi-directionalamplifiers 4122 may boost and even split the signal. Taps 4132 alongbranches provide connections to subscriber's homes 4142 and businesses.

Upstream transmissions from subscribers to the hub 4202/headend 4012occur by passing through the same coaxial cable 4302 as the downstreamsignals, in the opposite direction on a different frequency band. Theupstream signals may be sent typically utilizing Quadrature AmplitudeModulation (QAM) with forward error correction. The upstream signals canemploy QPSK or any level of QAM, including 8 QAM, 32 QAM, 64 QAM, 128QAM, 256 QAM, 512 QAM, 1024 QAM, and 4096 QAM. Modulation techniquessuch as Synchronous Code Division Multiple Access (S-CDMA) andOrthogonal Frequency Division Multiple Access (OFDMA) can also be used.Of course, any type of modulation technique can be used, as desired.

Upstream transmissions, in this embodiment, can be sent in afrequency/time division multiplexing access (FDMA/TDMA) scheme. Thediplexer 4092 splits the lower frequency signals from the higherfrequency signals so that the lower frequency, upstream signals can beapplied to the electrical to optical converter 4072 in the upstreampath. The electrical to optical converter 4072 converts the upstreamelectrical signals to light waves which are sent through fiber opticcable 4052 and received by optical to electrical converter 4032 in thenode 4202. The fiber optic links 4052 and 4062 are typically driven bylaser diodes, such as Fabry Perot and distributed feedback laser diodes.

FIG. 18 is a block diagram of an exemplary wireless service link. Thewireless service link may include a mediator 1013 in communication withan MTS 1063. It will be understood that mediator 1013 may be integratedwith or communicatively coupled with MTS 1063. The MTS 1063 may be, forexample, a CMTS, a Fiber Node, a Fiber Hub, an optical network unit(ONU), or other termination device. Mediator 1013 may be implemented,for example, as a software agent in any of such devices. If mediator1013 is integrated with an MTS, integration may be via software orhardware.

A UE 1053 may wirelessly communicate with other UEs (not shown) in awireless service network for the purpose of transmitting and/orreceiving data. A mobile core 1073 (e.g., operated by an MNO) controlsthe operations of the UE 105 within the wireless network. This includes,among other things, managing subscription information (e.g., datacommunication, data plans, roaming, international calling, etc.) andensuring that the UE 1053 can initiate or receive data sessions andtransmit data within the wireless network.

Mediator 1013 is implemented with a Communication Session System (CSS)1043 having a CSS interceptor 1083 and a CSS processor. Mediator 1013,via CSS 1043, is operable to intercept and process messages, such as butnot limited to LTE messages, between UE 1053 and mobile core 1073. CSSinterceptor 1083 is operable to intercept a request for a wirelesssession between UE 105 and the mobile core 1073 servicing UE 1053. In anembodiment, CSS processor 1093 processes CSS interceptor 1083intercepted setup information from the mobile core 1073, which isgenerated in response to the request. Based on the intercepted setupinformation CSS processor 1093 initiates a backhaul communicationsession (also called a “communication session” herein) between the modem1023 and the MTS 1063 to deliver the wireless session through thecommunication session. CSS processor 1093 initiates the communicationsession prior to, during, or close in time to when the wireless sessionis set-up such that the set-up process time, that of both thecommunication session and the wireless session, is reduced. In oneembodiment, the set-up of the backhaul communication session and thewireless session occur at least partially in parallel, thereby reducingthe set-up process time.

The CSS 1043 may process the intercepted message and generate orotherwise provide data to MTS 1063 such that MTS 1063 may establish acommunication session and a Quality of Service for the communicationsession between itself and the modem 1023. This may be done prior to, inparallel to, or close in time to the establishment of a wireless sessionby the mobile core 1073 with UE 1053, see below for more details. One ormore of the components of the mediator 1013 and CSS 1043 may beintegrated or in communication with the MTS 1063 via hardware, software,or combinations thereof.

In the past, MNOs often maintained, operated, and controlled wirelessbase stations themselves for the purposes of providing communicationswith UEs. For example, an MNO employing LTE communications may operate aplurality of eNodeBs in an area to provide wireless services tosubscribing UEs in that area.

Now operators are capable of acting as backhaul operators. For example,MSOs are seeking to increase their value to the MNOs by providingalternative backhaul paths for communication between UEs, such as UE1053, and the mobile core, such as mobile core 1073. MSOs and wirelessoperators currently employ wireless devices, a non-limiting example ofwhich is small cell 1033, for capturing a wireless data transmission andpassing it through a backhaul system, such as that shown in FIG. 18. Inthe embodiment of FIG. 18, the backhaul system includes modem 1023, MTS1063, and optionally meditator 1013. The small cell 1033 comprises manyof the features of a larger base station such as the air-to-airinterface and protocol handling. In some instances, the small cell 1033may be a multi-radio hotspot providing for Wi-Fi, as well as LTELicensed Assisted Access (LTE-LAA) or LTE Unlicensed (LTE-U).

In an alternative embodiment communication is Wi-Fi communication and isbetween a STA (not shown) a Wi-Fi core (not shown). To modify the systemof FIG. 18 to accommodate the Wi-Fi embodiment the skilled artisan wouldreplace small cell 1033 with a Wi-Fi station (STA) and the mobile core1073 with a Wi-Fi core.

Small cells and similar wireless technologies (collectively discussedand represented herein as small cells) represent new opportunities forMNOs. These new small cells allow operators to use existing spectrummore efficiently, and promote greater deployment flexibility, all at alower cost. Small cells also reduce radio access network build-out whileimproving the end user experience by providing increased access tomobile networks. Additionally, because small cells are much smaller,they can reduce a base station's footprint and have less environmentalimpact (e.g., in terms of power consumption).

The MSOs and MNOs, evolving from different technologies, generallyemploy different communication protocols and offer little insight toeach other. For example, the MSOs may employ the DOCSIS protocol totransport data to and from the modem 1023. The MNOs, on the other hand,may employ a variety of wireless protocols including EDGE (Enhanced Datarates for GSM Evolution), 2G, 3G, 4G, 5G, LTE, or the like. While theMTS 1063 and the modem 1023 may be able to transport the wirelessservice traffic of the UE 1053 and the mobile core 1073, the MTS 1063and the modem 1023 need not process the data transmitted. Rather, theMTS 1063 and the modem 1023 may simply route the traffic between theappropriate parties. In the example of FIG. 18, traffic is routedbetween UE 1053 and mobile core 1073 via small cell 1033, modem 1023,and MTS 1063.

When a UE or a mobile core wants to establish a communication sessionwith the other, the UE, small cell and mobile core exchange datasessions establishment with control signaling that includes QoSparameters. The QoS parameters describe a service quality for the datatransmitted over the impending wireless session. To transport thewireless traffic of the UE 105 and the mobile core 1073, the MTS 1063and the modem 1023 need to establish a communication session that allowsa wireless session between the UE 1053 and the mobile core 1073 tooccur. To ensure Quality of Experience (QoE) for the end user thatconsume the wireless session, the backhaul link between the MTS 1063 andthe modem 1023 should have matching or similar QoS provisions as the QoSrequirements exchanged between the UE 1053 and mobile core 1073.

However, the QoS information contained in the LTE signaling is unknownby the backhaul system. Since the MTS 1063 and the modem 1023 areunaware of the underlying wireless traffic, the MTS 1063 and the modem1023 do not know when a wireless session is being established. So, theMTS 106 and the modem 1023 cannot understand what types of Quality ofService (QoS) need to be employed. For example, in LTE, the mobile core1073 may need to establish QoS parameters for the UE 1053 based on thesubscription information of the UE 1053 and the type of media beingrequested by the application in use by the UE 1053. LTE identifies QoSwith a QoS Class Identifier (QCI), and can employ traffic prioritizationsuch as Allocation and Retention Priority (ARP), a Guaranteed Bit Rate(GBR), a Maximum Bit Rate (MBR), an Access Point Name-Aggregate MaximumBit Rate (APN-AMBR), a UE-AMBR, or some combination thereof.

This lack of insight by the backhaul system into the wireless sessionsetup process and the associated QoS requirement for the session,affects the ability of the backhaul system to provide adequate QoS onthe communication link between the modem 1023 and the MTS 1063. In caseof high priority high bandwidth applications such as live videostreaming, the MTS 1063 is not aware of the QoS requirements needed totransport the data between itself and the modem 1023. Thus, some blocksof data may be delayed such that they may no longer be relevant to thevideo and are therefore dropped. When this occurs regularly, the qualityof a live streaming video and the user's quality of experience (QoE) aredegraded significantly.

Now, even if the MTS 1063 becomes aware of the QoS requirement for thesession requested by either the UE 105, or the mobile core 1073, thetime it takes to set up adequate QoS provisions between the MTS 1063 andthe modem 1023 adds latency to the existing wireless session setupprocess. Consequently, the end user's wireless session start time isdelayed due to the serial setup processes (e.g., due to serial setupprocedure of LTE and DOCSIS sessions), and the user's QoE is stillaffected.

The present embodiments provide for the backhaul QoS signaling (e.g.,via a DOCSIS protocol) to be completed in parallel with the wirelesssession establishment (e.g., LTE wireless session establishment). Thepresent embodiments therefore enable the backhaul system to become awareof the QoS requirement for the wireless traffic such that they providefor the provisioning of the wireless session(s) accordingly, as well asenables the provisioning process to occur without added latency.

In this embodiment, the MTS 1063 is configured to identify the variousaspects of the wireless session. For example, the MTS 1063 may include amediator 1013 comprising functionality of a gateway. In this regard, theMTS 1063 can intercept a request from the UE 1053 (e.g., via the CSS1043) that indicates whether the UE 1053 needs to establish a session totransfer data to the mobile core 1073. This may direct the MTS 1063 toinitiate the establishment of a communication session between the MTS1063 and the modem 1023.

Alternatively or additionally, the MTS 1063 may be configured withfunctionality of the mobile core 1073 to decode and interpret LTEmessages. For example, in a DOCSIS protocol embodiment, the MTS 1063 isa CMTS, and may include functionality of an LTE gateway that is operableto intercept a session establishment request from the UE 1053 indicatingthat it needs to start a wireless session to the mobile core 1073. Thismay direct the MTS 1063 to initiate the establishment of a communicationsession between the MTS 1063 and the modem 1023.

The MTS 1063, mediator 1013, and/or CSS 10 3 may also intercept aresponse to the request from the mobile core 1073 (e.g., via mediator1013 or CSS 1043). For example, when the mobile core 1073 receives arequest from the UE 1053, the mobile core 1073 establishes the requestedwireless session between the mobile core 1073 and the UE 1053. This mayinclude establishing the parameters of the QoS for the wireless session.The MTS 1063 may intercept this information and initiate the setup ofthe communication session between the MTS 1063 and the modem 1023 usingthose QoS parameters for the wireless session to ensure that the user ofthe UE 1053 has an acceptable QoE. The MTS 106 and the modem 1023 worktogether to ensure that the QoS of the transport properly matches orsupports the QoS of the wireless session. The MTS 106 and the modem 1023do so without unnecessarily consuming or reserving too many networkresources. The operator determines how the QoS mechanism is applied tosupport the QoS Class Identifiers (QCIs), and configures these policyrules into the gateway, allowing the operator to optimize resources forQoS on their network.

Alternatively or additionally, the mobile core 1073 may communicate outof band signaling (00B) indicating that a wireless session between themobile core 1073 and the UE 1053 is to be established. The MTS 1063,mediator 1013, and/or CSS 1043 are operable to detect that signaling andinitiate or participate in the establishment of a communication sessionbetween the MTS 1063 and modem 1023 to accommodate the wireless session.

Because the MTS 1063, mediator 1013, and/or CSS 1043 intercepts thewireless session set-up data during the initiation of the wirelesssession, the communication session with the needed QoS can beestablished in parallel or at least partially in parallel to thewireless session rather than in series. For example, some operators mayuse DOCSIS network for backhauling traffic of the mobile core 1073.DOCSIS and radio networks, such as LTE, have separate schedulingalgorithms that result in longer communication latencies. That is, aradio network schedules traffic from the UE 1053 differently than anMTS, such as an CMTS, schedules traffic from the modem 1023. This oftenresults in the mobile core 107 needing to wait until the DOCSIS networkcompletes a session establishment before the proper QoS sessionestablishment can be completed. These embodiments overcome that byallowing the MTS 106 to establish the communication session with themodem 1023 substantially in parallel with the mobile core 1073establishing the wireless session with the UE 1053.

Based on the foregoing, the UE 1053 is any device, system, software, orcombination thereof operable to communicate wirelessly with a wirelessnetwork using any one or more wireless protocols including, 2G, 3G, 4G,5G, LTE, LTE-U, LTE-LAA, or the like, as well as with a Wi-Fi networkusing any one or more wireless service protocols including 802.11ax.Examples of the UE 1053 include, but are not limited to, laptopcomputers, tablet computers, and wireless telephones such as smartphones. The small cell 1033 is any device, system, software, orcombination thereof operable to provide an air-to-air interface 1103 forthe mobile core 1073, one example of which is a Wi-Fi core. Examples ofthe small cell 103 include Wi-Fi access points and base stationsoperating as eNodeBs in a wireless network. The modem 1023 is anydevice, system, software, or combination thereof operable to providedata transfers with an MTS. Examples of the modem 102 include DOCSISenabled set-top boxes, a Optical Network Unit or fiber optic modem, anda satellite modem. The MTS 1063 is any device, system, software, orcombination thereof operable to communicate with the modem 1023 as wellas provide a wireless service session through the communication linkprovided by the modem 1023 and the MTS 1063.

Again, the CSS 1043 and its components may implement the functionalityfor establishing the communication session setup stated herein. The CSS1043 may be any device, system, software, or combination thereofoperable with or in the mediator 1013 and/or the MTS 1063 to implementsaid functionality. Other exemplary embodiments are shown and describedbelow.

FIG. 19 is a flowchart illustrating an exemplary process 2003 operablewith the MTS 1063 of FIG. 18. In this embodiment, the small cell 103communicates with the UE 1053 over the air-to-air interface 1103 andforwards any UE data to the modem 1023. The modem 1023 may forward thedata to the MTS 1063. The CSS 104 receives the data, in the processelement 2013, and determines whether the data includes a request for awireless session, in the process element 2023. For example, the CSS 1043may evaluate all or a portion of the data from the UE 10533 anddetermine whether the UE 1053 is transmitting a request to the mobilecore 1073 such that the mobile core 1073 can establish a wirelesssession with UE 1053. Optionally mediator 1013, which in iscommunication with MTS 1063, determines whether the data includes arequest for a wireless session.

If it is determined in process element 2023, the data from the UE 1053does not contain such a request, the CSS 1043 simply forwards the datato the mobile core 1073 servicing the UE 1053, in the process element2033, and process 2003 ends. If it is determined in process element2023, the data from the UE 1053 does include a request to establish awireless session, then the CSS 1043 forwards, or is optionallyinstructed by the mediator 1013 to forward, the request to the mobilecore 1073, in the process element 2043. In an embodiment the CSS 104 mayinspect traffic from the mobile core 1073 intended for the UE 1053. Inthis regard, the CSS 1043 may intercept setup information for wirelesssession from the mobile core 1073, in the process element 2053.

The CSS 1043 propagates the setup information to the modem 1023 suchthat it may forward the setup information to the small cell 1033 and tothe UE 1053 over the air-to air-interface 1103. This allows the mobilecore 1073 to setup a wireless session with the UE 105. As the CSS 1043has determined that the mobile core 1073 is setting up the wirelesssession with UE 1053, the CSS 1043 initiates a communication sessionbetween the MTS 106 and the modem 1023 based on the intercepted setupinformation, in the process element 2063. Thus, the MTS 1063 sets up itscommunication session with the modem 102 while the mobile core 107 issetting up its wireless session with the UE 1053, thereby reducinglatencies associated with the differences between the wireless andwireline protocols.

FIG. 20 is an exemplary communication diagram of the wireless servicelink of FIG. 18. In this embodiment, the small cell 1033 communicateswith the UE 1053 over the air-to-air interface 1103 via a wirelessprotocol. Thus, when the UE 1053 communicates with the mobile core 1073,the UE 1053 communicates via the wireless protocol.

When the UE 1053 launches an application, the application may request anew wireless session through the mobile core 1073. Accordingly, the UE1053 transfers a bearer resource allocation request to the mobile core1073 via the small cell 1033. The small cell 1033 forwards the requestto the modem 1023. The modem 1023 forwards the request onto the MTS 1063over the communication link. The MTS 1063 or an associated mediator 1013(e.g., via the functionality of the CSS 1043) may intercept the request(element 1203) and recognize it as a bearer resource allocation requestfrom the UE 1053. This would allow the MTS 1063 or the associatedmediator 1013, independently or cooperatively, to prepare for a responsefrom the mobile core 1073 indicating that is about to establish awireless session with the UE 1053.

The MTS 1063 or the associated mediator 1013 (e.g., via thefunctionality of the CSS 1043), independently or cooperatively, forwardsthe request to the mobile core 1073 and waits for the associatedresponse. When the mobile core 1073 transfers a dedicated bearer contextactivation (e.g., an Evolved Packet System (EPS) bearer contextactivation), the MTS 1063 intercepts that activation message (element1213) and processes all or a portion of the message to access todetermine that the mobile core 1073 is establishing a wireless sessionwith the UE 1053. Accordingly, the MTS 1063 extracts activation messagedata, such as but not limited to the QoS parameters, from the activationmessage. The MTS 1063 does this to establish, for example, the same orcompatible QoS parameters with the communication session between the MTS1063 and the modem 1023. Then, the MTS 1063 establishes a communicationsession between the MTS 1063 and the modem 1023 (e.g., via a DOCSISDynamic Service Flow (DSx) message), as well as forwards the activationmessage to the small cell 1033, which in turn forwards it to the UE1053. Thus, the MTS 1063 establishes the setup of communication sessionafter or substantially at the same time the wireless session isfinalized. Once the wireless session is established, wirelesscommunications can commence between the UE 1053 and the mobile core 1073because the communication session between the MTS 1063 and the modem1023 has already been established.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. Embodiments utilizing network functionsvirtualization (NFV) and virtualized hardware, such as a virtualizedMTS, modem, etc., are also contemplated. In one embodiment, theinvention is implemented in whole or in part in software, which includesbut is not limited to firmware, resident software, microcode, etc. FIG.21 illustrates a computing system 3003 in which a computer readablemedium 3063 may provide instructions for performing any of the methodsdisclosed herein.

Furthermore, the invention can take the form of a computer programproduct accessible from the computer readable medium 3063 providingprogram code for use by or in connection with a computer or anyinstruction execution system. For the purposes of this description, thecomputer readable medium 306 can be any apparatus that can tangiblystore the program for use by or in connection with the instructionexecution system, apparatus, or device, including the computer system3003.

The medium 3036 can be any tangible electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system (or apparatus ordevice). Examples of a computer readable medium 3063 include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Some examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

The computing system 3003, suitable for storing and/or executing programcode, can include one or more processors 3023 coupled directly orindirectly to memory 3083 through a system bus 3103. The memory 3083 caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode is retrieved from bulk storage during execution. Input/output orI/O devices 3043 (including but not limited to keyboards, displays,pointing devices, etc.) can be coupled to the system either directly orthrough intervening I/O controllers. Network adapters may also becoupled to the system to enable the computing system 3003 to becomecoupled to other data processing systems, such as through host systemsinterfaces 3123, or remote printers or storage devices throughintervening private or public networks. Modems and Ethernet cards arejust a few of the currently available types of network adapters.

FIG. 22 is a block diagram of an exemplary system operable to providewireless service for a plurality of UEs 1053-1-1053-N (where “N” issimply intended to represent an integer greater than “1” and notnecessarily equal to any other “N” reference designated herein). Forexample, upstream and downstream links of the exemplary communicationsystem offers high speed data services over connected devices, such asthe modem 1023. The modem 1023 may be configured with or receivecommunications from the small cell 1033 so as to allow the UEs 1053 tocommunicate through the communication system in a manner that istransparent to the user.

The communication system includes a communication component 4013configured with an upstream hub 4203. The hub 4203 is coupled to a fibernode 4213 via optical communication links 4053 and 4063. The hub 4203includes an MTS 1063, an electrical to optical converter 4033, and anoptical to electrical converter 4043. The node 4213 is similarlyconfigured with an optical to electrical converter 4083 and anelectrical to optical converter 4073.

The communication component 4013 is the source for various communicationsignals. Antennas may receive communication signals that are convertedas necessary and transmitted over fiber optic cables 4053 to the hub4203. Several hubs may be connected to a single communication component401 and the hub 4203 may each be connected to several nodes 4213 byfiber optic cable links 4053 and 4063. The MTS 1063 may be configured inthe communication component 4013 or in the hub 4203.

Downstream, such as in homes/businesses, are devices that operate asdata terminals. These data terminals are modems. A modem can acts as ahost for an Internet Protocol (IP) device such as personal computer.However, the modem can be configured with a small cell so as to providewireless services through the system for the UEs 1053-1-1053-N.

In this embodiment, transmissions from the MTS 1063 to the modem 102 arecarried over the downstream portion of the communication systemgenerally in the band between 54 MHz and 3 GHz, for example. Downstreamdigital transmissions are continuous and are typically monitored by manymodems. Upstream transmissions from the modems to the MTS 1063 are, forexample, typically carried in the 5-600 MHz frequency band, the upstreambandwidth being shared by the Modems that are on-line. However, withgreater demands for data, additional frequency bands and bandwidths arecontinuously being deployed in the downstream and upstream paths. It isalso possible that modems 1023 and the MTS 1063 engage in full duplextransmission modes, whereby concurrent transmissions on the upstream andthe downstream over the same frequency is supported. Equivalentcommunications and protocols for fiber optic transmissions are alsocontemplated, for example, using an optical network terminal (ONT) oroptical line termination (OLT), and an optical network unit (ONU), andequivalent protocols such as EPON, RFOG, or GPON.

The MTS 1063 connects the system to the Internet backbone. The MTS 106connects to the downstream path through an electrical to opticalconverter 4043 that is connected to the fiber optic cable 4306, which inturn, is connected to an optical to electrical converter 4083 at thenode 4213. The signal is transmitted to a diplexer 4093 that combinesthe upstream and downstream signals onto a single cable. The diplexer4093 allows the different frequency bands to be combined onto the samecable.

After the downstream signal leaves the node 4213, the signal istypically carried by a coaxial cable 4303. At various stages, a powerinserter 4103 may be used to power the coaxial line equipment, such asamplifiers or other equipment. The signal may be split with a splitter4113 to branch the signal. Further, at various locations, bi-directionalamplifiers 4123 may boost and even split the signal. Taps 4133 alongbranches provide connections to subscriber's homes 4143 and businesses.

Upstream transmissions from subscribers to the hub 4203/headend 4013occur by passing through the same coaxial cable 4303 as the downstreamsignals, in the opposite direction on a different frequency band. Theupstream signals are sent typically utilizing Quadrature AmplitudeModulation (QAM) with forward error correction. The upstream signals canemploy QPSK or any level of QAM, including 8 QAM, 32 QAM, 64 QAM, 128QAM, 256 QAM, 512 QAM, 1024 QAM, and 4096 QAM. Modulation techniquessuch as Synchronous Code Division Multiple Access (S-CDMA) andOrthogonal Frequency Division Multiple Access (OFDMA) can also be used.Of course, any type of modulation technique can be used, as desired.

Upstream transmissions, in this embodiment, can be sent in afrequency/time division multiplexing access (FDMA/TDMA) scheme, orOrthogonal Frequency Division Multiple Access (OFDMA). The diplexer 4093splits the lower frequency signals from the higher frequency signals sothat the lower frequency, upstream signals can be applied to theelectrical to optical converter 4073 in the upstream path. Theelectrical to optical converter 4073 converts the upstream electricalsignals to light waves which are sent through fiber optic cable 4053 andreceived by optical to electrical converter 4033 in the node 4203. Thefiber optic links 4053 and 4063 are typically driven by laser diodes,such as Fabry Perot and distributed feedback laser diodes.

FIG. 23 is an exemplary communication diagram of the wireless servicelink employing Wi-Fi. In FIG. 23, the communication diagram isillustrated as part of a Wi-Fi association setup. In this regard, thecommunication link established between the modem 1023 and the MTS 1063interfaces with a Wi-Fi core 5013 as well as an access point (AP) 5023(e.g., wireless access point or “WAP”). The AP 5023 communicates with aWi-Fi station (STA) 5033 such that the STA 5033 can transmit data to theWi-Fi core 5013.

When the STA 5033 needs to transmit data to the Wi-Fi core 5013, the STA5033 issues an “association request” to the AP 502.3. The AP 5023transfers the association request to the modem 1023 which, in turn,issues a request to the MTS 1063 to transfer data. The MTS 1063transfers a MAP (or some other granting mechanism) to the modem 1023granting the modem 1023 a data transfer. At or about the same time, theAP 5023 communicates with the STA 5033 as part of a security processuntil the AP 5023 accepts the association with the STA 5033.

When the AP 5023 accepts the association with the STA 5033, the AP 502forwards the accepted association to the modem 1023 such that it maytransfer the accepted association to the MTS 1063. The MTS 1063transfers a MAP (or some other granting mechanism) to the modem 1023such that it can prepare for the data from the STA 5033. And, when theSTA 5033 receives the accepted association from the AP 5023, the STA5033 begins to transfer its data. As the communication link between themodem 1023 and the MTS 1063 has already been established, the AP 5023can simply transfer the data to the Wi-Fi core 5013 through the grantedcommunication link between the modem 1023 and the MTS 1063.

FIG. 24 is an exemplary communication diagram of the wireless servicelink of FIG. 18 illustrating a network initiated session. In thisembodiment, the mobile core 1073 transfers a bearer alert to the MTS1063. The MTS 1063 may intercept the alert (element 1303) and recognizeit as a network initiated bearer alert for the UE 1053. This would allowthe MTS 1063 to prepare to respond to the impending wireless sessionestablishment by preparing to set up a communication session on betweenthe MTS 1063 and the modem 1023. The MTS 1063 then transfers the alertto the UE 1053 through the modem 1023 and the small cell 1033. Again,the small cell 1033 communicates with the UE 1053 over the air-to-airinterface 1103 via a wireless protocol. Thus, when the UE 1053communicates with the mobile core 1073, the UE 1053 communicates via thewireless protocol. From there, the mobile core 1073 transfers adedicated bearer context activation (e.g., a Evolved Packet System (EPS)bearer context activation), the MTS 1063 intercepts that activationmessage (element 1213) and understands that the mobile core 1073 isestablishing a wireless session with the UE 1053, and in turn, initiatesa session setup on the communication link (e.g., via DSx for DOCSIS).The communications continue as with that shown and described in FIG. 20.

FIG. 25 shows one exemplary communication system 100 in which thepresent prioritized grant assignment system and method may be utilized.

As shown, communication system 1004 includes User Equipment (UEs)1024(1)-1024(n), a small cell 1104, a backhaul system 1204 configuredwith a modem 1224 and a modem terminal system (MTS) 1244, and a wirelesscore 1304 (hereinafter core 1304). It will be understood that UEs1024(1)-1024(n) may be any user equipment or radio terminal, such ascell phones, laptop computers, tablet computers, wearables, Internet ofThings (IoT) devices, a wireless equipped motor vehicle, etc. Inaddition, small cell 1104 may be any wireless access base station, forexample, an eNodeB, a Wi-Fi access point, etc. Furthermore, UE's 1024'sand small cell 1104 may be configured with one or more wirelesscommunication protocols, example of which include but are not limited toWi-Fi, 3G, 4G, 5G, and Long Term Evolution (LTE) communicationprotocols. Core 1304 may be any core that services radio terminalssimilar to UEs 1024, such as a mobile core, a Wi-Fi core, or the like.As discussed above, backhaul system 1204 may be any system capable ofwireless backhauling data.

In an embodiment, small cell 1104 and modem 1224 are co-located. In sucha version, small cell 1104 and modem 1224 may be configured within thesame enclosure.

It will be understood that MTS 1244 may be formed as a single device ormay be formed as more than one device. Alternatively, MTS 1244 may beformed as a combination of real and virtual devices, virtual components,and/or virtualized functions. If virtualization is utilized, suchvirtual devices, components, and/or functions maybe executed within thebackhaul system or may be implemented outside of the backhaul system.

UEs 1024 are in wireless communication via communication link 1404 withsmall cell 1104. Small cell 1104 is in wired or wireless communicationwith backhaul system 1204 via communication link 1424. Backhaul system1204 is in wired communication with core 1304 via communication link1444.

As suggested above, the invention, in total or in part, may take theform of an entirely hardware implementation, an entirely softwareimplementation or an embodiment containing both hardware and softwareelements. Embodiments utilizing network functions virtualization (NFV)and virtualized hardware, such as a virtualized MTS, virtualized modem,virtualized aspects of the MTS and/or modem, etc., are alsocontemplated. In one embodiment, the invention is implemented in wholeor in part in software, which includes but is not limited to firmware,resident software, microcode, etc.

FIG. 26A is a detailed view of some aspects of the prioritized grantassignment system of FIG. 25. System 1004 of FIG. 26 is described hereprocessing multiple buffer status reports (BSRs) 2264 to generate a bulkrequest (REQ) 2704 for resources from a connected backhaul system 1204,in an embodiment.

Each UE 1024(1)-(n) is configured with an input/output (IO) system 2024,a CPU 2044, a wireless transceiver 2064, and a memory 2204, all of whichare communicatively coupled. More or fewer components may beincorporated within a UE 1024 without departing from the scope herein.I/O 2024 may be any device level input/output system, including but notlimited to a keyboard, mouse, touch screen, display, tactic feedbacksystem, monitors (e.g., heart rate, Global Positioning (GSP), activitysensor, accelerometer, any health monitoring system, position sensors asused in room scale virtual reality (VR), etc.), graphics cards, soundcard, I/O chips and/or chip sets, etc. I/O 2024 may also be removablyand/or temporality coupled with UE 1024. Processor 2044 may be aprocessing unit including but not limited to one or more of a centralprocessing unit, a microprocessing unit, a graphics processing unit(GPU), a multi-core processor, a virtual CPU, a control unit, anarithmetic logic unit, a parallel processing unit or system, etc.Transceiver 2064 may be any or a plurality of wireless transceiverscapable of wirelessly communication with the small cell 1104 on one ormore compatible wireless communication protocols. Memory 2204 may be anynon-transitory memory. Memory 2204 may also be a plurality ofcooperative memory components. Memory 2204 may be implemented as orinclude one or more buffers. However, memory 2204 is organized BSR 2264describes at least a portion of it for purposes of requesting resourcesfrom one or more networks to transmit data stored therein.

Memory 2204 stores at least a buffer status report (BSR) 2264, a data2244 for transmission across backhaul system 1204 to core 1304, and oneor more wireless grants 2224. It will be understood that BSR 2264(1),data 2244(1), and wireless grant 2224(1) are specific to UE 1024(1) andBSR 2264(n), data 2244(n), and wireless grant 2224(n) are specific to UE1024(n) and may be erased, written over, or moved to a secondary storagedevice (not shown) at a time determined by UE 1024 or any decisionmaking units within system 1004, such as modem 1224, MTS 1244, and core1204. Wireless grants 2224(1) and 2224(n) are shown in dashed line torepresent that they are only present after BSRs 2264(1) and 2264(n) aresent to and processed by small cell 1104, which generates wirelessgrants 2224(1) and 2224(n) and transmits them back to UEs 1024(1) and1024(n), respectively. This process may be seen at least in FIGS. 28A-B.

Data 2244(1) and data 2244(n) are of a certain size, shown here ashaving size of A bytes for data 2244(a) and B bytes for data 2244(n).Data in data 2244 is organized by priority, for example into logicalchannel groups (LCG) 0-3. Logical channel grouping is the prioritizationscheme utilized in the present embodiments shown here, but it wouldapparent to the skilled artisan that another prioritization scheme maybe used without departing from the scope herein. Throughout the presentdescription LCG0 is assigned the highest priority data, LCG 1 isassigned the next lowest priority, etc. Examples of data that would beplaced into LCG0 are control messages specific to the wireless network,mission critical traffic, gaming traffic, or anything that requires thelowest latency. Examples of data that would be placed into LCG1 arevoice or video traffic. Examples of data that would be placed into LCG2are data traffic from such applications as web browsing. Examples ofdata that would be placed into LCG3 are low priority background traffic,examples of which include but are not limited to file uploads, filedownloads, and software updates. BSRs 2264(1)-(n) contain at leastmetadata describing the size of the data contained within each of theirrespective data 2244 (1)-(n) such that any intermediate and/or receivingsystems may utilize this metadata to provide a grant for all or aportion of the data in data 2244(1)-(n). As will be discussed below, ifthe provided grant cannot accommodate all the data is a data 2244 or thecombination of data contained with a plurality of data 2244 s, then thesystem groups and data in prioritized the data based on LCG, see belowfor more details.

Small cell 1104 is shown to include an I/O 2524, a CPU 2544, adownstream transceiver 2564, an upstream transceiver 2574, a priorityprocessor 2584, a bulk request (REQ) module 259,4 and memory 2604. I/O2524 may be any I/O system similar to that described for I/O 202. CPU2544 may be any processing unit similar to that described for CPU 1044.Memory 2604 may be any memory similar to that described for memory 2204.

Downstream transceiver 2564 may be any of, or a plurality of, wirelesstransceivers capable of wirelessly communication with the UEs1024(1)-(n) and other devices utilizing one or more compatible wirelesscommunication protocols.

Upstream transceiver 2574 is shown as a wireline communication unit.Alternatively upstream transceiver 2574 may be a wireless transceiverfor communicatively coupling with backhaul system 1204, for example tomodem 1224. Upstream transceiver 2574 utilizes a backhaul 1204compatible communication protocol. As such, small cell 1104 maytranslate, repackage, and/or reorganize data received from one or moreof UEs 1024(1)-(n) into one or more backhaul compatible data units orstreams. Furthermore, the present system and method may translate,repackage, and/or reorganize the data in concert with the presentprioritized grant assignment system and method.

Priority processor 2584 repackages data received from UEs 1024, such asdata 2244(1)-(n), into prioritized based on logical channel groups. Thefunctionality of priority processor 2584 will be detailed further in theFIG. 26B and its associated description.

Bulk REQ module 2594 combines each BSR 2264(1)-(n) received from UEs1024(1)-(n) into a single BSR, a bulk REQ 2704, for transmission tobackhaul system 1204's MTS 1244 which results in a backhaul grant tomodem 1224, discussed later. This ensures the backhaul system 1204 isprepared to forward all or a portion of data 2244(1)-(n) upon receipt atmodem 1224. MTS 1244 processes bulk REQ 2704 and, based on networkparameters such as available capacity, rate limits based on ServiceLevel Agreements for the UEs being serviced on the small cell, orprioritization of traffic of the small cell compared to other smallcells provides small cell 1104 a grant that accommodates all or aportion of the request for resources defined by bulk REQ 2704. FIGS. 27and 28A describe an instance where processing bulk REQ 2704 results in agrant that completely satisfies the request. FIG. 28B describe aninstance where processing bulk REQ 2704 results in a grant thatpartially satisfies the request.

The remaining description for FIG. 26A will focus on UE 1024(1),although it will be understood that the description is equally relevantto any of UEs 1024(2)-1024(n). UE 1024(1) is shown having data 2244(1),which is ready for transmission to core 1304, stored in memory 2204(1).As described above, BSR 2264(1) is also stored in memory 2204, describesdata 2244. In its most basic implementation, BSR 2264(1) describes theamount of data in data 2244, e.g., A bytes of data. In a more detailedembodiment, BSR 2264(1) may describe the amount of data in eachLCG0-LCG3. For example, data 2244(1)'s LCG0 data may have X1 bytes ofdata, LCG1 data may have Y1 bytes of data, LCG2 data may have Z1 bytesof data, and LCG3 data may have W1 bytes of data, such thatX_1+Y_1+Z_1+W_1=A bytes of data at a minimum. Upon receiving a grant totransmit it BSR 2264(1), UE 1024(1) sends BSR 2264(1) to small cell 1104via wireless connection 1404. Small cell 1104 receives BSR 2264(1) atdownstream receiver 2564 at which point it is moved to memory 2604 asBSR 2264(1). As described above, UE 1024(n) utilizes the same process,which results in BSR 2264(n) being stored in memory 2604 with BSR2264(1).

Small cell 1104 then process BSRs 2264(1)-(n) to generate wirelessgrants 2224(1) and 2224(n) and sends these back to UEs 1024(1) and1024(n) respectively.

Substantially close in time to the generation and transmission ofwireless grants 2224(1) and 2224(n) to UE 1024(1) and UE 1024(n),respectively, bulk REQ module 2594 takes BSR 2264(1)-2264(n) as inputsand combines them to produce bulk REQ 2704. Bulk REQ 2704 is thentransmitted to MTS 1244 in backhaul system 1204 via upstream transceiver2574, communication link 1424, and modem 1224. MTS 1244 processes bulkREQ 2704 to produce bulk grant bulk grant 2804 (see FIGS. 27 and28A-28B). Bulk grant 2804 is sent to small cell 1104 via modem 1224 andlink 1424. Bulk grant 2804 may accommodate all or a portion of the datawithin data 2244(1)-(n), depending on network resources available. Asdescribed above, this ensures the backhaul system 1204 is prepared toforward the allotted amount of data 2244(1)-(n) upon receipt at modem1224. Small cell 1104 processes bulk grant 2804 to ascertain theresources available to it.

If bulk grant 2804 only provides resources for small cell 1104 totransmit only a portion of data 2224(1)-(n) then the present system andmethod operates to ensure the highest priority data, namely LCG0 data,is prioritized first, followed by LCG1, then LCG2, and finally LCG3.This will be discussed in more detail below.

In an embodiment, not shown here, the functionality and associatedhardware and/or software described above for small cell 1104 mayalternatively be configured with and implemented by modem 1224. That is,modem 1224 may by formed with I/O 2524, CPU 2544, downstream transceiver2564, upstream transceiver 2574, priority processor 2584, bulk request(REQ) module 2594, and memory 2604 such that modem 1224 performs theoperations described above and below with modification that would beobvious to the skilled artisan. It will be understood that such anembodiment does not preclude modem 1224 from being a virtualized modem1224, in whole or in part. Furthermore, it will be understood that asmall cell 1104 implementation does not preclude small cell 1104 fromalso being a virtualized at least in part.

FIG. 26B shows system 1004 of FIG. 26A after the receipt of wirelessgrant 2224(1) and 2224(n) at UES 1024(1) and 1024(n), respectively, andbulk grant 2804 at small cell 1104. Furthermore, system 1004 of FIG. 26Bis shown transmitting data 2244(1) and (n) from UEs 1024(1) and 1024(n)to small cell 1104. Data 2244(1) and 2244(n) are stored in memory 2604.Because bulk grant 280 is in place when data 2244(1)-(n) arrives atsmall cell 1104 all or a portion of that data, depending on the grant,may be transmitted to core 1304 vie backhaul system 1204.

If bulk grant 2804 can accommodate all of data 2244(1) and 2244(n), thatis A bytes+B bytes, then no further processing is requires and data224(1)-2244(n) is transmitted to core 1304 via backhaul system 1204utilizing standard methods of repackaging or translating wireless data2244(1)-2244(n) in to a backhaul compatible container or data.

Alternatively, if bulk grant 2804 cannot accommodate all of data2244(1)-2244(n), then priority process 258 acts on data 2244(1)-2244(n),discussed in more detail in at least FIG. 27.

FIG. 27 shows one exemplary priority processing module 2584 configuredwithin small cell 1104, which processes upstream data for transmissionafter the receipt of bulk grant 2804, which is only a partial grant.

Priority module 2584 is shown including a priority processor 3004 and aprioritized data-grant fit module 3204. Priority processing 2584,priority processor 3004, and prioritized data-grant fit module 3204 maybe implemented as a single combined device or component, as standalonedevices, or may be implemented, separately or together, as functionalityexecuted by CPU 2544.

Priority processor 3004 is represented to include a logical channel (LC)grouper 3044 and LCG0 3064-LCG3 3094.

LCG0 3064 is a buffer or temporary data storage for UE 1024(1)-1024(n)'sLCG0 data. LCG1 3074 is a buffer or temporary data storage for UE1024(1)-1024(n)'s LCG1 data. LCG2 3084 is a buffer or temporary datastorage for UE 1024(1)-1024(n)'s LCG2 data. LCG3 3094 is buffer ortemporary data storage for UE 1024(1)-1024(n)'s LCG3 data.

LC grouper 3044 takes all data 2244 at its input and stores, copies orotherwise records each UE 1024's LCG data into the appropriate LCG03064-LCG3 3094 temporary storage. For example, LC grouper 304 processdata 224(1) and data 2244(n) and copies all LCG0 data to LCG0 3064. Thatis, LC grouper 3044 copies data 2244(1)'s LCG0_1 data and data 2244(n)'sLCG_N data in LCG0 3064. LC grouper 3044 similarly copies all data2244(1)'s and data 2244(n)'s LCG1 data to LCG1 3074, all data 2244(1)'sand data 2244(n)'s LCG2 data to LCG2 3084, and all data 2244(1)'s anddata 2244(n)'s LCG3 data to LCG3 3094. CLG0 3064-LCG3 3094 are thencopied to prioritized data-grant fit 3224 as LCG0 3364-LCG3 3394.

Prioritized data-grant fit module 3224 is shown to be configured with amemory 3244, an upstream fit calculator (UFC) 3264, and a transmitbuffer 3284. Memory 3244 has stored with in it bulk grant 2804 which wasgenerated by MTS 1244, and LCG0 3364-LCG3 3394. Bulk grant 2804 of FIG.27 is a grant for an amount of data equal to C+D bytes of data, which isa portion of that requested, namely A+B bytes of data. C+D bytes of dataand A+B bytes of data are symbolically represented in transmit buffer3284, more on this below.

Transmit buffer is shown including LCG0_1, LCG0_N, LCG1_1, LCG1_N,LCG2_1, LCG2_N, LCG3_1, and LCG3_N. The size of LCG0_1, LCG0_N, LCG1_1,LCG LN, LCG2_1, LCG2_N, LCG3_1, and LCG3_N is equal to A+B bytes, thesize of the bulk REQ 270. The size of LCG0_1, LCG0_N, LCG1_1, LCG1_N,LCG2_1, and LCG2_N is equal to C+D bytes, the size of the bulk grant2804. C+D<A+B.

UFC 3264 takes as inputs bulk grant 2804 and LCG0 3364, LCG1 3374, LCG23384, and LCG3 3394. UFC 3264 then process the LCG0 3364, LCG1 3374,LCG2 3384, LCG3 3394 data, and bulk grant 2804 to determine which datacan be accommodated by bulk grant 2804 for the related transmission.This process may be as simple as determining the size of bulk grant 2804(C+D bytes) and perform arithmetic calculations to with LCG0, LCG1,LCG2, LCG3 in order of priority to determine which data packages can beaccommodated by the bulk grant 2804. Another exemplary process is a UEprioritization process, which may order LCG data based on Service LevelAgreement or priority, such that if C+D bytes of data provided by bulkgrant 4804 is not sufficient to serve all UE logical channel group data,then LCG data is prioritized by UEs such that higher priority UEs havetheir data accommodated first. Furthermore, UE prioritization may bemulti-tiered such that LCG0 data from first priority UEs are handledfirst, then LCG0 data from second priority UEs are handled next, and soforth. In an embodiment, LCG1 data originating from a highest priorityUE is handled before LCG0 data from a second tier UE. Determining thepriority of UEs may be based on the type of device (e.g., emergencyservices devices autonomous vehicles have a higher priority thanstandard user devices and IoT devices), a user or user accountassociated with the device (e.g., a business or premium account versusan individual account or lower tier account, or military account versusa civilian account), order of association with the small cell, etc.Other processes are detail below.

In the embodiment of FIG. 27 bulk grant 2804 may accommodate C+D bytesof data, which provides for the transmission of LCG0_1, LCG0_N, LCG1_1,LCG1_N, LCG2_1, and LCG2_N over backhaul system 120. LCG3_1 and LCG3_Nmay be shifted the next or subsequent bulk request and upstreamtransmission. Alternatively, LCG3_1 and LCG3_N may be dropped, forexample, if that data is determined to be stale.

FIG. 28A is a communication diagram 4004 for system 1004 in thesituation where all of a request conveyed by a Bulk REQ 2704 is granted,in an embodiment. In the present embodiment two UEs are shown, UEs1024(1) and 1024(n). As discussed above, it will be understood that moreUEs may participate in the present system and method without departingfrom the scope here and only two are shown and described here to reducecomplexity and increase understanding. FIG. 28A is best understood whenread in combination with FIGS. 26A-B and 27.

In diagram 4004 UEs 1024(1) and 1024(n) transmit service requests (SRs)SR1 UE1 4024 and SR2 UE2 4044 to small cell 1104 to request a grant forthe transmission of each UEs buffer status report (BSR), BSR 2264(1) andBSR 2264(n), see FIGS. 26A, 26B, and 3. Small cell 1104 receives andprocesses SR1 UE1 4024 and SR2 UE2 4044, producing two BSR grants, BSRGrant UE1 4064 and BSR Grant UE2 4084, which are sent back to therespective UE. UE 1024(1) and 1024(n) receive and process the BSR grants4064, 4084 and transmit BSR 2264(1) and BSR 2264(n). BSR 2264(1) conveysto small cell 1104 that UE 1024(1) has A bytes of data in its bufferwhere and BSR 2264(n) conveys to small cell 1104 that UE 1024(n) has Bbytes of date in its buffer. A and B, which describe the A and B bytesof data, are numeric variables which designate the size or amount ofdata stored in the respective buffers. Small cell 1104 processes BSR2264(1) and 2264(n) and produces a grant for each UE 1024, grant 2224(1)and grant 2224(n). In addition, small cell 1104 generates bulk REQ 2704.Bulk REQ 2704 is a request for backhaul system 1204 resources totransmit the combination of at least data 2244(1) and 2244(n) (or anydata 2244(1)-(n) if more UEs 1104 are associated with small cell 1104and have data in their buffers to transmit). Small cell 1104 transmitsgrants 2224(1) and 2224(n) to UEs 1024(1) and 1024(n), respectively, andbulk REQ 2704 to MTS 1244 via modem 1224 within backhaul system 1204.The order the UE Grants 2224 and the bulk REQ 2704 are produced andtransmitted by small cell 1004 may vary according to implementation aslong as they occur substantially close enough in time such that a bulkgrant, one example of which is bulk grant 2804 as shown in FIGS. 26B, 27and 28A, may be received and processed by small cell 1104 prior to thereceipt of data from the UEs, such as data 2244(1)-(n) discussed in moredetail below. Although not ideal, it will be consistent with the presentinvention if bulk grant 2804 is received at small cell 1104 after thereceipt of data 2244(1) and 2244(n) at small cell 1104 as long as it isnot so long after that there is no reduction in latency over the serialgrant assignment utilized in the prior art. Upon receipt of the grants2224(1) and 2224(n), UE 1024(1) and UE 1024(n) prepare data 2244(1) and2244(n), respectively, for transmission.

In an embodiment, UEs 1024(1) and 1024(n) also include new BSRs in data2244(1) and 2244(n), shown in diagram 4004 as BSR_A and BSR_B. In suchan embodiment grants 2224(1) and 2224(n) include additional resources toaccommodate BSR_A and BSR_B. BSR_A and BSR_B are requests for resourcesto transmit new data in UE 1024(a) and 1024(n)'s buffers that wasgenerated after the transmission of SR1 UE1 4024 and SR2 UE2 4044. This“piggy backing” process reduces the need to go through the SR/BSR-grantprocess (described above) for the next and potentially subsequent datatransmissions.

Upon receipt of data 2244(1) and 2244(n) and bulk grant 2804 at smallcell 1104 the small cell packages 4124 data 2244(1) and 2244(n), forexample in a manner similar to that shown and described for FIG. 27, fortransmission to core 1304 via backhaul system 1204. In an embodimentthat includes BSR_A and BSR_B, small cell 1104 may also process BSR_Aand BSR_B in a similar fashion as described above for BSR 2264(1) and2264(n), producing new grants 4224(1) and 4224(n) and a second bulk REQ4704.

This second bulk REQ 4704 may be transmitted separately from (as shownin FIG. 28) or packaged with the upstream transmission of data 2244(1)and 2244(n) (not shown) to MTS 2244 on its way to core 1304. If secondbulk REQ 4704 is transmitted separately from the upstream transmissionof data 224(1) and 2244(n) to core 1304, as shown is in FIG. 28, thenBSR_A and BSR_B may be processed before or after the upstreamtransmission of data 2244(1) and 2244(n) from small cell 1104 to core1304.

If the second bulk REQ 4704 is sent with the upstream transmission ofdata 2244(1) and 2244(n) then bulk grant 2804 must include additionalresources to accommodate bulk REQ 4704, that is bulk grant 2804 must becapable of accommodating at least A bytes+B bytes+X bytes, where X bytesis at least the amount of data need to accommodate bulk REQ 4704, e.g.,a summary of BSR_A and BSR_B. With bulk REQ 4704 sent with or proximatein time to the upstream transmission of data 2244(1) and 2244(n), MTS1244 may read or extract bulk REQ 4704 upon receipt of the upstreamtransmission of data 2244(1), data 2244(n), and the bulk REQ 4704. BulkREQ 4704 may be packaged with data 2244(1) and 2244(n) such that MTS1244 can only read bulk REQ 4704, which utilizes a backhaul 1204 formator protocol, and MTS 1244 may not read data 2244(1) and 2244(n), whichutilizes a core 1304 format or protocol different from that of backhaul1204's format or protocol.

FIG. 28B is a communication diagram 4504 for the present grantassignment process wherein only a portion of the request conveyed by aBulk REQ is granted, in an embodiment.

Communication diagram 4504 is similar to communication diagram 4004 upuntil the receipt of bulk REQ 2704 by MTS 1244 from small cell 1104. Assuch all steps prior to the receipt of bulk REQ 2704 by MTS 1244 indiagram 4504 are not described here for the sake of brevity. Diagram4504 differs from diagram 4004 in that MTS 1244 processes the receivedbulk REQ 2704 to produce a bulk grant 4804 which accommodates less datathan that requested in bulk REQ 2704. That is diagram 4504 shows ascenario where backhaul system 1204 can only accommodate a portion ofbulk REQ 2704, which requests resources to transmit A+B bytes of data.Thus MTS 1244 generates a bulk grant 4804, similar to bulk grant 2804 ofFIG. 27, which accommodates C+D bytes of data, which is less A+B bytes:(C+D<A+B).

Bulk grant 4804 is transmitted to small cell 1104 via modem 1224.Substantially concurrently to the transmission and processing of bulkREQ 2704 and generation of bulk grant 4804, UEs 1024(1) and 1024(n)process grants 2224(1) and 2224(n), prepare data 2244(1) and 2244(n) andoptionally new BSRs BSR_A and BSR_B, and transmits these to small cell110, as similarly described from diagram 4004, FIG. 28A.

As similarly described in FIG. 27, small cell 1104 performs a logicalchannel grouping process ad prioritized grant fit process as describedin FIG. 27. That is, the priority processor 3004 groups together all LCG0 data from each UE 1024's data 2244, all LCG1 data from each UE 1024'sdata 2244, etc. The prioritized data-grant fit 3224 unit the fits theLCG data to the bulk grant 2804, 4804 such that data with the highestpriority, LCG0 Data, is prioritized for transmission, followed by LCG1,LCG2, etc. In the situation of FIG. 28B (and FIG. 27) not all data canbe transmitted under bulk grant 4804, namely LCG3_1 and LCG3_N data. Assuch, LCG3_1 and LCG3_N data are subsequently retained in the transmitbuffer 3284, memory 2640, or a similar generic or dedicated memory,which may or may not be shown.

The remaining LCG data is then packaged 4544 and transmitted to mobilecore 1304 via modem 1224 and MTS 1244 of backhaul system 1204.Optionally, and as similarly described for FIG. 28A, small cell 1104 mayalso process new BSRs, BSR_A and BSR_B, and provide grants 4224(1) and4224(n) to UEs 1024(1) and 1024(n).

FIGS. 29A-C describe a method 5004 detailing one exemplary process forgenerating a bulk request for resources, in an embodiment. FIGS. 29A-Care best viewed together.

Step 5024 of method 5004 receives an SR1 and an SR2 from UE1 and UE2,respectively. An example of step 5024 is UEs 1024(1) and 1024(n)transmitting SR1 UE1 4024 and SR2 UE2 4044 to small cell 1104, as shownand described in FIGS. 28A and 28B.

Step 5044 of method 5004 sends a BSR Grant to both UE1 and UE2. Anexample of step 5044 is small cell 1104 transmitting BSR grant UE1 4064and BSR grant UE2 4084 to UE 1024(1) and UE 1024(n), respectively.

Optional step 5064 of method 5004 determines what resources areavailable to small cell in preparation for processing the forthcomingBSRs from the UEs. An example of step 5064 is small cell 1104 analyzingits available resource for comparison to the BSRs received from UEs1024(1) and 1024(n) in step 5084-5104.

Step 5084 of method 5400 receives BSR1 and BSR2 from UE1 and UE2,respectively. An example of step 5084 is small cell 1104 receiving BSR2264(1) and 2264(n) from UEs 1024(1) and 1024(n), respectively.

Optional step 5104 of method 5004 compares the optional step 5064determined available resources to the step 5084 received BSRs (BSR1 andBSR2) to determine if the small cell has resources to accommodate the UErequests. An example of step 5104 is small cell comparing itspredetermined available resources with the received BSRs 2264(1) and2246(n) to determine if resources are available and when they areavailable.

Decision step 5124 of method 5004 determines if and when resources areavailable to accommodate the BSRs. If resources are available method5004 moves to step 5144. If resources are not available, method 5004moves to step 5424 of FIG. 29B, described below. An example of step 5124is small cell 1104 producing a result as to the available resources andacting on that result by initiating either the process of step 5144 or5404, FIG. 29B.

Step 5144 of method 5004 generates a UE1 Grant and a UE2 Grant toaccommodate all data requested by BSR1 and BSR2. An example of step 5144is small cell 1104 producing a grant 2224(1) for UE 1024(1) and a grant2224(n) for UE 1024(n).

Step 5164 of method 5004 combines all grants, e.g., UE1 grant and UE2grant, to generate a bulk backhaul request and transmits the bulkbackhaul request to the processing aspect of the backhaul system. Anexample of step 5164 is small cell 1104 combining grants 2224(1) and2224(n) as described, for example, in FIGS. 27 and 28A and 4B, toproduce and transmit bulk REQ 270 to MTS 1244 via modem 1224. It will beunderstood that other backhaul components may be involved in theprocess, for example, if alternative backhaul systems are used, e.g.,any backhaul system that relies on a request grant protocol.

Step 5184 of method 5004 sends UE1 grant to UE1 and UE2 grant to UE2. Anexample of step 5184 is small cell 1104 transmitting grant 2224(1) and2224(n) to UE 1024(1) and 1024(N), respectively.

Step 5204 of method 5004 receives bulk grant from backhaul system. Anexample of step 5204 is MTS generating a bulk grant 2804 is thenreceived by small cell 1104 from MTS 1244 via modem 1224.

Step 5224 of method 5004 receives UE1 and UE 2 data and optionallyreceive a second BSR1 from UE1 and a second BSR2 from UE2. An example ofstep 5204 is small cell 1104 receiving data 2244(1) and 2244(n) from UEs1024(1) and 1024(n), respectively. Optionally, small cell 1104 may alsoreceive a new BSR from UE 1024(1), BSR_A, and a new BSR from UE 1024(n),BSR_B.

Step 5244 of method 5004 process bulk grant and bulk request todetermine if the bulk grant accommodates all of UE1 and UE 2 Data. Anexample of step 5224 is small cell 1004 determining if the bulk grantreceived in step 5204 satisfies the bulk REQ 2704, sent is step 5164.

Decision step 5264 of method 5004 provides a decision based on theresults of step 5244, determining if the bulk grant accommodates all ofUE1 and UE 2 Data. If it is determined that the bulk grant does notaccommodate all of the data described in the bulk request, decisionmethod 5004 moves to step 5504 of FIG. 29C, described further below. Ifstep 5264 determines that the bulk grant satisfies the bulk request,then method 5004 moves to step 5284. An example of step 5244 is smallcell 1104 processing the result of a comparison between the bulk grantand the bulk request.

Step 5284 of method 5004 groups UE1 data and UE2 data for transmissionto the mobile core via backhaul system. One example of step 5284 issmall cell 1104 packaging data A+B 412, as described in FIG. 28A.

Step 5304 of method 5004 transmits UE1 Data and UE2 Data to the MobileCore via the Backhaul system. One example of step 530 is small cell 110transmitting data 2244(1)+2244(n) to mobile core via modem 2224, MTS2244, and core 1304, as described in FIG. 28A.

FIG. 29B shows a method 5404, which branches from step 5124 of method5004, FIG. 29A, for handling a partial small cell grant.

In step 5424 method 5404 generate a UE1 and UE2 partial grant toaccommodate a portion of the request resources as described in BSR1 andBSR2. One example of step 5424 is small cell processing the results ofstep 506 and BSR 2264(1) and BSR 2264(n) to generate a partial grant forBSR 2264(1) and a partial grant for BSR 2264(n).

In step 5444 method 5404 combines UE1 and UE2 partial grants to generatebulk request and transmits the bulk request to the backhaul system forprocessing. One example of step 5444 is small cell 1104 combiningpartial grants (not shown) to produce a bulk request, similar to bulkREQ 2704, and transmitting it to MTS 1244 via modem 1224.

In Step 5464 method 5404 transmits the partial grants, generated in step5424, to UE1 UE2. One example of step 5464 is small cell 1104transmitting partial grants, similar to grants 2224(1) and 2224(n), toUEs 1024(1) and 1024(n).

In step 5484 method 5404 receives a bulk grant from the backhaul system.Note example of step 5484 is small cell 1104 receives a bulk grant,similar to bulk grant 2804 of FIG. 28A, from MTS 1244 via modem 1224.

In step 5504 method 5404 receive data and optionally new BSRs from theUEs. One example of step 5504 is small cell 1104 receiving data, similarto data 2244(1) and 2244(n) from UEs 1024(1) and 1024(n). Method 5404then moves to step 5244 of FIG. 28B.

FIG. 29B shows a method 5604, which branches from step 5264 of method5004, FIG. 29A, for handling a partial backhaul grant.

In step 5624 method 5604 performs a logical channel grouping by groupingtogether all UE data by Logical Channel Group (LCG) such that, forexample, all UE1-UEn data designated as Logical Channel Group 0 (LCG0)are grouped together, all UE1-UEn data designated as Logical ChannelGroup 1 (LCG1) are grouped together, etc. One example of step 5624 LCgrouper 3044 taking in data 2244(1) and 2244(n) and placing LCG0_1 datawith LCG0_n data in LCG0 3064, placing LCG1_1 data with LCG1_n data inLCG1 3074, placing LCG2_1 data with LCG2_n data in LCG2 3084, placingLCG3_1 data with LCG3_n data in LCG3 3094, as described in FIGS. 27 and28B. Alternatively, metadata describing LCG0-LCG3 may be groupedtogether or otherwise organized for analysis in the later steps ofmethod 5604 to determine what LCG data the grant may accommodate.

In step 5644 method 5604 performs an upstream fit calculus by analyzingif the bulk grant can accommodate the LCG0 data. Method 5604 then movesto decision step 5664 where method 5604 makes a decision based on theresult of step 5644. If the bulk grant cannot accommodate all of theLCG0 data then method 5604 moves to step 5904, where method 5604 buffersany un-accommodated LCG data for later transmission.

Alternatively, if the bulk grant cannot accommodate all of the LCG0 datathen method 5604 may perform a second analysis (not shown) to determineif the bulk grant can accommodate LCG0 data from a UE in order ofpriority. For example, UE1 (e.g., a medical device) may have a higherpriority than UE2 (e.g., a gaming device) such that if the bulk grantcannot accommodate all of LCG0 data (e.g., UE1 LCG0 data plus UE2 LCG0data) then method 5604 may determine if the bulk grant can accommodateLCG0 data from high priority UE1 only. If the bulk grant can onlyaccommodate UE1 LCG0 data, then method 5604 moves UE2 LCG0 data to step5904, buffering it for later transmission and UE1 LCG0 data is movedthrough the rest of method 5604 or just prepared for transmission if thebulk grant cannot accommodate any other data. Although it will not berepeated again, the above alternative process may be included with anysimilar steps described below.

If it is determined in step 5664 that the bulk grant can accommodate allof the LCG0 data then decision step 5664 moves to step 5674.

In step 5674 method 5604 prepares the LCG0 data for transmission. Oneexample of step 5674 is LCG0_1 and LCG0_n data sent to transmit buffer3284, FIG. 27.

In step 5684 method 5604 performs an upstream fit calculus by analyzingif the bulk grant can accommodate the LCG1 data. Method 5604 then movesto decision step 5704 where method 5604 makes a decision based on theresult of step 5684. If the bulk grant cannot accommodate all of theLCG1 data then method 5604 moves to step 5904, where method 5604 buffersany un-accommodated LCG data for later transmission. If it is determinedin step 5704 that the bulk grant can accommodate all of the LCG1 datathen decision step 5704 moves to step 5714.

In step 5714 method 5604 prepares the LCG1 data for transmission. Oneexample of step 5714 is LCG1_1 and LCG1_n data sent to transmit buffer3284, FIG. 27.

In step 5724 method 5604 performs an upstream fit calculus by analyzingif the bulk grant can accommodate the LCG2 data. Method 5604 then movesto decision step 5744 where method 5604 makes a decision based on theresult of step 5724. If the bulk grant cannot accommodate all of theLCG2 data then method 5604 moves to step 5904, where method 5604 buffersany un-accommodated LCG data for later transmission. If it is determinedin step 5744 that the bulk grant can accommodate all of the LCG1 datathen decision step 5744 moves to step 5754.

In step 5754 method 5604 prepares the LCG2 data for transmission. Oneexample of step 5754 is LCG2_1 and LCG2_n data sent to transmit buffer3284, FIG. 27.

In step 5764 method 5604 performs an upstream fit calculus by analyzingif the bulk grant can accommodate the LCG3 data. Method 5604 then movesto decision step 5784 where method 5604 makes a decision based on theresult of step 5764. If the bulk grant cannot accommodate all of theLCG3 data then method 5604 moves to step 5904, where method 5604 buffersany un-accommodated LCG data for later transmission. If it is determinedin step 5784 that the bulk grant can accommodate all of the LCG3 datathen decision step 5784 moves to step 579.4

In step 5794 method 5604 prepares the LCG3 data for transmission. Oneexample of step 5794 is LCG3_1 and LCG3_n data sent to transmit buffer3284, FIG. 27.

In step 5804 all data that can be accommodated by the bulk grant issent, via the backhaul system to its destination, e.g., a mobile orWi-Fi core.

It is not necessary that the steps described here for method 5604 beperformed in the order described. For example, all processing steps maybe performed prior to all decision steps. Furthermore, additional stepsmay be included that are not shown. For example, the method andassociated system may package any buffered un-accommodated data suchthat the packaged data may be easily added to a forth coming backhaulbulk request. The method and associated system may also monitor theportions of data within the buffered un-accommodated data to determineif any of that data has become “stale.” Any stale data may be removedand the remaining data may be repackaged so it may be added to any forthcoming backhaul bulk request.

Changes may be made in the above methods and systems without departingfrom the scope hereof. It should thus be noted that the matter containedin the above description or shown in the accompanying drawings should beinterpreted as illustrative and not in a limiting sense. The followingclaims are intended to cover all generic and specific features describedherein, as well as all statements of the scope of the present method andsystem, which, as a matter of language, might be said to fall therebetween.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms of the invention. Rather,the words used in the specification are words of description rather thanlimitation, and it is understood that various changes may be madewithout departing from the spirit and scope of the invention.Additionally, the features of various implementing embodiments may becombined to form further embodiments of the invention.

What is claimed is:
 1. A method for reducing latency in wireless servicethrough a protocol communication link comprising a Modem TerminationSystem (MTS) and a modem, the method operable at the modem andcomprising: detecting a message from a user equipment indicating thatthe user equipment has data to transmit to a mobile core network;requesting to transfer the data of the user equipment to a Gateway inresponse to detecting the message from the user equipment; andprocessing a grant from the Gateway to transfer the data of the userequipment to the Gateway while the user equipment is negotiating withthe mobile core network to transmit the data of the user equipment. 2.The method of claim 1, wherein: the message is a scheduling request (SR)of a Long Term Evolution (LTE) wireless protocol.
 3. The method of claim1, wherein: the message is a buffer status report (BSR) of a Long TermEvolution (LTE) wireless protocol indicating an amount and a quality ofservice (QoS) requirement of the data of the user equipment to betransmitted.
 4. The method of claim 1, wherein: the message is a LTEgrant of a Long Term Evolution (LTE) wireless protocol indicating anamount of the data of the UE to be transmitted, and a precise time thedata of the UE to be transmitted.
 5. The method of claim 1, wherein: themessage is formatted according to a WiFi protocol.
 6. The method ofclaim 1, further comprising: conveying an amount and a quality ofservice (QoS) assignment of the data of the user equipment to the MTS totrigger the MTS to deliver a QoS grant granting the amount and the QoSassignment of the data, and a timing of the grant.
 7. The method ofclaim 1, wherein: detecting is performed by an eNodeB communicativelycoupled to the modem; and the method further comprises transferring thedata of the user equipment from the eNodeB to the MTS over a Data OverCable Service Interface Specification (DOCSIS) link when the userequipment finishes negotiating with the wireless service link.
 8. Themethod of claim 1, wherein: the message includes information pertainingto a plurality of buffer status reports (BSRs) of a Long Term Evolution(LTE) wireless protocol indicating an amount and quality of service(QoS) requirement of data of a plurality of user equipment to betransmitted.
 9. The method of claim 1, wherein: the message includesinformation pertaining to a plurality of LTE grants of a Long TermEvolution (LTE) wireless protocol indicating an amount of the data ofthe plurality of user equipment to be transmitted, and a precise timethe data of the plurality of user equipment to be transmitted.
 10. Themethod of claim 1, wherein: the message is formatted according to a WiFiprotocol.
 11. A method for reducing latency in wireless service linkthrough a communication link comprising a Modem Termination System (MTS)and a modem, the method operable at the MTS and comprising: processing arequest from the modem, wherein the request indicates that a userequipment (UE) has data to transmit to a mobile core network; grantingthe request while the UE is negotiating with a Gateway to transmit thedata of the UE; receiving the data of the UE from the modem; andtransferring the data of the UE to the mobile core network.
 12. Themethod of claim 11, wherein: the request from the modem is in responseto a scheduling request (SR) of a Long Term Evolution (LTE) wirelessprotocol from the UE.
 13. The method of claim 11, wherein: the requestfrom the modem is in response to a buffer status report (BSR) of a LongTerm Evolution (LTE) wireless protocol indicating an amount and aquality of service (QoS) requirement of the data of the UE is to betransmitted.
 14. The method of claim 11, wherein: the request from themodem is in response to LTE grant of a Long Term Evolution (LTE)wireless protocol indicating an amount of the data of the UE that is tobe transmitted, and a precise time the data of the UE that is to betransmitted.
 15. The method of claim 11, further comprising: processingthe amount of the data of the UE to be transmitted to the mobile corenetwork via the modem; and configuring subsequent grants based on theamount and a quality of service (QoS) requirement of the data.
 16. Themethod of claim 11, further comprising: processing an amount of the dataof the UE from the modem; and configuring subsequent grants based on theamount and a quality of service (QoS) assignment of the data, and aprecise timing of the grant.
 17. The method of claim 11, furthercomprising: transferring the data of the UE from the modem to the mobilecore network. 18.-112. (canceled)